Air taxi flight crew reported during takeoff an aircraft crossed the runway requiring evasive action action to avoid a collision. The flight crew of the crossing aircraft stated they did not hear the other aircraft announcing takeoff.

Date: 2025-12 · Aircraft: Metro Undifferentiated or Other Model · Phase: takeoff

Anomalies: aircraft-equipment-problem-less-severe|conflict-ground-conflict|critical|ground-incursion-runway

Synopsis

Air taxi flight crew reported during takeoff an aircraft crossed the runway requiring evasive action action to avoid a collision. The flight crew of the crossing aircraft stated they did not hear the other aircraft announcing takeoff.

Narrative

While conducting a training flight at ZZZ; I experienced a Category A/B runway incursion from an approaching aircraft on a perpendicular taxiway during the takeoff roll from RWYXX. Acting as pilot flying and receiving instruction; we had been conducting training flights for several hours that morning in and around the ZZZ area. Winds were calm; visibility unlimited; and the sky was clear of clouds. As such; multiple aircraft were in the vicinity of the airport conducting training; as well as scheduled and non-scheduled passenger operations arriving and departing. All runways were available; however; RWYXX was in use by most general aviation traffic; so I opted to use RWYXX for takeoff and landing. After arriving from an instrument approach followed by a landing to RWYXX; I exited the runway at TWY 1 and continued via TWY2 to the hold short line of RWYXX at 3 to prepare for another departure. While running the appropriate after-landing and before-takeoff checklists; I announced our intentions and position reports on CTAF along the way as we exited; taxied; and then held short of the runway demarcation bars. At this time; a C56X was approaching from the south to RWYXY and a Part 121 B737 was on a long final for RWYXZ. After preparing for takeoff I announced that we were holding short of RWYXX for departure and waiting for the C56X on short final to RWYXY to land. After seeing the jet touch down on the runway; I lost contact with the aircraft as it exited onto TWY 4 so I queried the crew on CTAF of their position and intentions. I received no reply and waited several more seconds before I visually acquired them again southbound on the 4 TWY. After seeing their position; I determined the runway area was clear and announced on the CTAF that I was departing RWYXX and would make left-closed traffic to remain in the pattern for a landing. Throughout the takeoff roll; I continued to monitor the Citation Jet's relative position to the runway; assuming they would hold short of the active runway in use (XX) before crossing it at TWY 5 and continuing ahead to the FBO. Upon reaching 95 knots on the takeoff roll (approximately 3000' down the runway); I heard the approaching Citation Jet announce that they were crossing RWY XX/XA at TWY 5 as they rolled through the runway holding position bars. I quickly queued up on the CTAF frequency and said; 'STOP; STOP; STOP!' At this point; I was nearing the V1 decision speed and immediately determined that we would not be able to stop in time before colliding with the aircraft that had now entered the runway. In response; I moved the power levers forward to their limits and maneuvered the aircraft to the left side of runway while pulling the yoke back to rotate the aircraft. The aircraft lifted off the ground approximately abeam where the C56X had entered the runway on TWY 5 and the wingtip of the airplane narrowly missed the nose of the oncoming jet by less than 50'. I continued the takeoff and made an uneventful normal landing on RWY XX. A post-flight inspection of the aircraft revealed no damage.After securing the aircraft; my instructor and I approached the pilots of the Citation Jet to debrief with them and question their decision to enter the runway. The pilots of the other aircraft appeared defensive and stated they did not hear us making the call that we were taking off and departing from the runway. I then asked the pilots if they had looked for crossing traffic before entering the runway or heard our initial inquiry of their position before taking the runway for departure. The pilots stated they did look for traffic prior to crossing and did not see us approaching on the runway. They also said they did not hear our intentions to depart on the CTAF; however; they did hear my call several minutes prior that we were holding short of RWYXX.Upon reflection; I assume the pilots of the Citation Jet were task saturated with their after-landing procedures and were not able to notice my takeoff call prior to departure. Confirmation bias also likely played a role in their decision to cross the runway before determining it was clear based on their receipt of our holding short call while they were on final approach and landing. I also believe the incident could have been totally avoided if the pilots of the C56X had thoroughly looked both ways before deciding to cross the runway. After all; our aircraft was a large turboprop with many bright lights that was less than 500' away from them as they approached the runway.After debriefing with my instructor pilot and the pilots of the other aircraft; my key takeaway from the incident is it is important to maintain total vigilance when operating at busy uncontrolled airports with several runways in use. It is important to maintain situational awareness of all aircraft in the vicinity of the airport; especially when entering a runway. I also feel that my evasive actions as pilot flying were necessary to avoid a collision. Upon running stopping distance performance calculations with the input of our ADSB data from the flight; I determined that we would not have been able to stop in time to avoid a collision if the takeoff was aborted. Another outcome in a high-speed rejected takeoff like this could have been an intentional runway excursion in attempt to avoid a collision with the oncoming aircraft. This would have resulted in substantial damage or injury to us and our aircraft; and could have led to further impact of terrain and buildings surrounding the runways and taxiways.

Second reporter narrative

Holding short of runway XX in ZZZ; attempted to make contact on CTAF with a citation that was taxiing to the ramp from runway XZ. They did not respond. Upon visual contact; made the determination that it was safe and clear to depart runway XX for left closed traffic; subsequently made the CTAF call that we were taking the runway. On final portion of the takeoff roll; citation jet called crossing runway XX and began rolling onto active runway. We called to attempt to get them to stop; and knowing that we would not be able to stop in time; continued the takeoff. Sidestepped off centerline in further attempt to avoid collision. Achieved liftoff around taxiway 5 and avoided any further incident. Post flight; upon conversation with the flight crew of the citation; it was determined that they allegedly were unable to hear any of the calls we had made on CTAF. I'm of the opinion that the flight crew was potentially distracted and simply missed our calls; as we have been training at that field all week without any communication issues with other aircraft. For future prevention; I believe an extra level of focus and diligence should be maintained at uncontrolled fields; especially those with no fewer than two active runways during busy hours.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.