2024-04 · NASA ASRS report 2103809
Flight crew reported that another aircraft saw fire coming out of their left engine during take off roll. They rejected the takeoff and with the absence of fire warning or detection indications taxied back to the gate.
First flight of the day for this aircraft. We taxied the aircraft single engine to Runway XXL; started #1; and warmed it up for over seven minutes. There was a west crosswind with gusts to 25 knots. We were cleared for takeoff at the taxiway. We did a rolling takeoff; and during the roll we overheard an (other carrier) Pilot telling the Tower that he saw a flame coming out of our left engine (and he indicated it did not seem normal). Tower called us to verify if we had heard (other carrier) Pilot. We checked cockpit indications; but saw nothing notable. I rejected the takeoff solely due to the visual report of fire.I initially thought we rejected at 80 knots; but the RTO (Rejected Takeoff) AUTO-BRAKE had engaged; so in hindsight it must have been closer to 90 knots. We slowly taxied clear; requested ARFF (Airport Rescue and Fire Fighters); and checked our Performance Data BRAKE COOLING module. Rescue examined the engine and detected nothing wrong. After I inquired; our B Flight Attendant informed me that a Passenger seated a few rows from the back had also claimed to notice sparks and a popping noise. Brake cooling (at 80 knots) stated that cooling was not required. We radioed for Maintenance and a gate; and shut down #1 Engine normally. We were followed by ARFF as we taxied to the gate uneventfully. Maintenance removed this aircraft from service.
Rejected a takeoff on runway XXL in ZZZ Airport due to a reported engine fire. Captain was operating as PF during this flight from ZZZ-ZZZ1. During the takeoff another aircraft stated our left engine had fire coming from the back of it. At approximately 90 knots we rejected the takeoff due to a suspected engine fire. The aircraft did not show any indications of an engine fire other than what the aircraft stated. Due to the absence of fire warning or detection indications; we exited the runway on Taxiway 1 and requested fire rescue. Fire rescue stated they did not observe a fire. We then completed brake cooling performance and taxied back to the gate without further incident.
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.