An air carrier flight crew reported a rejected takeoff when they observed an aircraft on short final in the opposite direction.
Synopsis
An air carrier flight crew reported a rejected takeoff when they observed an aircraft on short final in the opposite direction.
Narrative
Date/Flight Info:Day 0 | Flight ABCD | ZZZZ to ZZZNarrative:While operating flight ABCD; we taxied to Runway XX at ZZZZ after advising intentions on AFIS frequency XXX.X. A pop-up Tower Controller advised no reported traffic in the area" prior to taxi.After completing all pre-takeoff flows and checklists; and once lined up on Runway XX; the Captain/pilot flying (PF) set takeoff thrust. During the takeoff roll (approximately 50 KIAS); the Captain visually identified inbound traffic landing opposite direction on Runway XY. I (First Officer (FO)) confirmed the traffic by sight of its landing light; and immediately called for a rejected takeoff. The Captain simultaneously initiated a low-speed RTO (Rejected Takeoff); reducing thrust to idle; braking; and deploying max reverse.The aircraft on approach (later identified as Aircraft Y) was not on frequency and was roughly 200-500' AGL when the Captain advised them via radio to go-around. Still not on frequency; Aircraft Y then initiated its go-around. We subsequently back taxied and returned to the ramp to contact Dispatch and Maintenance Control; and allowed right main brake temps (amber range) to cool. Once cleared by Maintenance Control and with brakes cooled; we reattempted departure. Aircraft Y returned; joined the correct frequency (XXX.X); and safely landed Runway XX.Our departure/flight to ZZZ proceeded normally and uneventfully thereafter.Cause: Non-towered airport operations with ad hoc tower services; opposite direction traffic not monitoring/transmitting on published frequency; and lack of situational awareness by inbound traffic.Suggestions: Standardized pre-departure briefings to include vigilance for potential incoming opposite direction traffic when operating in/out of uncontrolled fields.Reinforcement and more explicit coordination with airport authorities and/or local ATC to ensure all aircraft are aware of the correct; published frequency required to be monitoring + transmitting on at uncontrolled fields via NOTAMs."
Second reporter narrative
Departing from ZZZZ we made all CTAF/AFIS calls and ZZZZ operations also confirmed no planes had called into the airport so the area was expected to be clear. Again after making the required calls we back taxied Runway XX the winds were 260 at 10kts. We lined up and began the takeoff. After our check thrust/ thrust checked call and monitoring engine gauges and airspeed while looking down the runway I noticed what looked like a landing light pop out of a scattered layer of clouds headed straight at us for the opposite runway. My First Officer (FO) confirmed it was a plane headed towards us I decided to reject the take off which was at around 50-60kts. We made calls on CTAF and the aircraft continued toward us on the runway. What looked like 500ft or lower we saw the plane turn and go around. They had made 0 CTAF calls including the Go around. Once we back taxied to the ramp to check things out; Aircraft Y then checked in on CTAF that they had gone around and were coming back for the other runway Runway XX. After verifying with the AOM; FOM; Dispatch and Maintenance we only had amber temps on one brake indicator and no EICAS messages so we let the brakes cool. Re ran all numbers and checklist and departed successfully to ZZZ.Cause: Aircraft Y made no radio calls and was descending through clouds to the runway that would not be in use. Winds were 260 at 10kts making Runway XX the clear choice.Suggestions: Airport needing radar and Tower. Airplanes making appropriate radio calls.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.