Runway Incursion Avoided by ATC
In the episode, I departed Hammond, Louisiana enroute to Nashville, Tennessee on a return flight after aircraft maintenance. ATC cleared me to takeoff, and asked me to “keep rolling” to expedite the takeoff due to an aircraft on a four mile final approach to the same runway.
I aborted the takeoff and then ATC instructed the inbound aircraft to go-around due to my aborted takeoff instruction. While the event was fairly benign, it was also abnormal. I was focused on the instrument panel and displays for the takeoff and did not see the reason for the cancelled takeoff clearance. I later reviewed the footage and zoomed in to the far end of the runway, where I saw a preceding aircraft exiting the runway. At the time of this video, I was unaware and, unfortunately, did not see the aircraft at the opposite end of the runway. The preceding aircraft was almost at the end of the runway when I rolled into position and I did not notice it until I review the footage during editing at the point the aircraft turned on the taxiway.
I don’t want to be overly dramatic because there was likely no chance of interference between the aircrafts, based upon timing, but ATC performed the correct action to cancel my takeoff clearance because another aircraft was still occupying the runway.
This video is a reminder to expect the unexpected and perform actions requested by ATC in a timely manner. We will also talk about obtaining all relevant information in preflight planning, a technique for backtaxiing on a runway, and high energy events in a SF50.
It would have definitely been clear if I would have been able to perform a static takeoff instead of expediting takeoff roll.
More information related to the 3-P Process and Flight Risk Assessment Tool (FRAT).
https://sf50flightsupport.com/aeronautical-decision-making-adm/
