A plane actually took off from the grass at Kennedy Airport.

Below are all the steps I took to trigger this bug, along with the issues encountered ・_・

During the period from 20:00 to 22:10, Flight ① was performing a "Runway Holding" procedure before Runway 22L. Due to another flight ② landing on Runway 22L, "Change Path" and "Hold Taxi" commands were issued to prevent Flight ① from taxiing onto the runway.During radio communication, Flight ① exhibited slight delay in taxiing. After its nose wheel crossed the current waypoint, it executed a path plan to re-approach via the "H" exit point at the takeoff point along Runway 22L (heading toward the holding point before Runway 22L).

I attempted to execute a "Permit Takeoff" command while Flight ① was taxiing, intending to halt its movement and initiate a direct takeoff.However , Flight ① showed no response and could not be halted via any command to stop takeoff or taxiing. Continuing its movement, it directly crossed Runway 22R and Runway 31R without triggering the runway crossing hold . Furthermore, while taxiing under an active takeoff clearance, it was identified as a "runway incursion" by Flight ④, which was executing its approach on Runway 22L.However, Flight ① was currently on the taxiway, merely carrying a takeoff command.

As it approached its original route plan (the holding point before the Runway 22L entry point), Flight ③ had just completed its "Hold on Runway" instruction and was awaiting takeoff. resulting in Flight ① completely ignoring Flight ③'s hold position. Instead, it executed a 90-degree turn just meters from the Runway 22L entry point, heading toward the grassy area left of Runway 22L for takeoff —utterly reckless! 😨

Recommend improving takeoff command options, such as adding "Prohibit Takeoff," "Pause Takeoff," or " Wait. " Otherwise, an accidental press of "Allow Takeoff" could immediately cause the aircraft's pathfinding to malfunction, indirectly leading to grass takeoff scenarios. 👿