2026-02 · NASA ASRS report 2330985
CRJ-200 flight crew reported a near collision with aircraft departing in opposite direction on landing roll out. Crew debriefed and continued trip.
During the landing rollout on Runway XX; an opposite direction single engine general aviation aircraft departed on Runway XY. The First Officer was PM and was communicating on CTAF with several aircraft on and in the vicinity of the field; but there was never any communication from the aircraft that departed opposite direction. Winds were 190 at 6 kts. All other traffic was landing and departing in the direction of the prevailing winds. Prior to our arrival; an aircraft departed Runway XZ. A med evac was holding short of Runway XX during our approach and landing. An inbound Baron several miles behind us was also landing XX. We were in constant communication with all of these aircraft. I landed on the 1000 foot markers; opened the single operable thrust reverser; and began braking. During the rollout; the opposite direction aircraft came into view on the runway and I braked aggressively. The departing aircraft rotated and immediately made a turn toward the east to avoid us and departed the area. The departing aircraft did not have lights on and it was getting close to sunset which contributed to us being unable to see the aircraft until the rollout. We were unable to identify the aircraft despite requesting assistance from other aircraft on CTAF; airport personnel; ATC; and electronic means such as FlightAware. We do not know if the aircraft departed from the airport or if they were transient and performed a touch and go.As a note; we did not receive a TCAS TA; but 'Traffic Proximity - TCAS TA' was the closest option to select.Cause: No communication from departing aircraft. No lighting on departing aircraft. Time of day (nearing sunset).Suggestions: Make radio communication on CTAF a requirement at all public use airports.
Visual approach into ZZZ via the RNAV XX track joining at ZZZZZ. Non-towered field with traffic holding short of XX and other traffic 20 miles away setting up for an approach to XX. Winds were 190 at 6 favoring a landing on XX. Communicated intentions and location at 30 miles; 15 miles; 10 miles joining final; 5 miles; and 2 miles short final landing less than a minute. Other traffic on frequency were coordinating. Another aircraft had departed XZ prior to our arrival that we were also communicating to. Positively visually identified traffic (med evac) holding short of our landing runway with Captain and verbalized 'traffic on the ground holding short in sight.' Time of day was approaching dusk so we turned the airport lighting to max brightness to help identify runway and PAPI's. Captain was PF and landed the plane on the 1000 ft markers as we were on a short runway with a single thrust reverser. On the rollout; I called out '90 kts.' then heard the Captain exclaim 'Oh my God!' as my eyes transitioned back outside and saw a single engine airplane departing opposite direction rotating 300-500 ft in front of us and veer off to the side to avoid hitting us. It did not appear to have any lights on. Captain was quick to react and slam on the brakes as I started communicating over CTAF to get the pilots attention and warn other traffic of a rogue airplane in the pattern not communicating. Both pretty shaken up we exited the runway and communicated further with other traffic on CTAF to possibly identify the pilot. The pilot who departed the opposite direction did not respond and was not identified. We canceled IFR and completed the remaining checklist. I performed post flight duties and the Captain communicated with the Manager and airport staff to get more information. We debriefed and continued the trip. No TCAS RA was received.Cause: Pilot not communicating in CTAF; pilot departing opposite direction; and improper lighting on aircraft made it hard to identify.Suggestions: CTAF usage needs to be enforceable on uncontrolled fields.
More incidents for this aircraft family
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.