2022-05 · NASA ASRS report 1900196
Air Carrier flight crew reported being notified by FA1 of a fume event during pushback. Flight crew executed a gate return for maintenance action. No definitive cause was determined but the forward galley oven was the likely cause.
Odor event happened during pushback. FA1 (Flight Attendant) called flight deck while we were pushing back to report passenger in 2D complained of unusual odor and FA1 confirmed the smell from the area of rows 2-4. In the flight deck we did not smell anything unusual. I informed FA1 that I would need to get back to her in a minute while I communicated with Push Crew to hold the push and stay connected while I investigate the odor report. I asked the Push Crew if they could see or smell anything unusual that might have caused FA1 to notice. From the Ground Crew there was nothing unusual. The aircraft was safely stopped and brakes set and I called back to FA1 to get update and investigate what was happening. The update from FA1 was unusual smell persisted. To investigate; I inquired about the oven possibly being the cause due to it was on earlier while at the gate to heat food. FA1 indicated a familiarity with that type of oven smell and was not the possible cause. Next asked about potential causes from overhead bin spill or passenger; but neither could be judged as the cause. FA1 indicated enough concern about the odor and unknown source to judge this an Odor Event and follow procedures. Coordinated return to the gate and informed Dispatch over ACARS; Operations and Maintenance over company radio. Referenced FOM Aircraft Smoke; Odor or Fumes; accomplished all the steps. I emphasized to my crew the duty to perform a self assessment and seek medical attention if needed. My PA included request for passenger self assessment/medical attention. I was later informed that FA1 and FA3 did seek medical. The entire event from push to block-in was 17 minutes.I could not smell anything so I was solely relying on reports from FA1 and the cabin crew. I suspect it was from the oven being used at the gate earlier. Perhaps the oven smell is quite different while it cools off on the ground; compared to how the smell is perceived during cruise. It could be the way cabin airflow subtly changed after the cabin door was shut for pushback; altering the perception of normal oven operation.Check how long it takes for an oven to cool off after use. The fans in the oven run after it is off and that time information could help alleviate any concerns about unusual odors during that time.
At XA30z we pushed back from [Gate] on our way to ZZZ1. After starting to push off the gate; but prior to engine start; we got a call from our #1 Flight Attendant about an odor in the cockpit. We finished the push back and advised the Ground Crew to stay connected and with us on the headset for a possible return to the gate. Immediately; we called back the cabin crew to discuss what they were experiencing. We were told by the Flight Attendants that there was an odor coming from the first class portion of the aircraft around rows 2-3. The odor was being experienced by both the two Flight Attendants who were at the forward part of the aircraft as well as some of the first class passengers. The odor was described by a passenger as smelling like oven cleaner or the burning smell of an iron and ironing board. There was some back and forth between us and the Cabin Crew as we worked to ask questions; get information; and determine the type and source of the possible odor. Around the same time that the Flight Attendant first called; both the Captain and I distinctly smelled the scent of the galley ovens. Prior to departing; the Flight Attendant had prepared our inflight meals since it was going to be a quick flight. We later learned that one of the Flight Attendants had her food inside the oven and Maintenance also later confirmed that at least one oven was on when they arrived to meet the aircraft during deplaning. As we were getting the information from the Flight Attendants I worked to coordinate a return to the gate; and called Maintenance. I also turned to the Smoke/AVIONICS SMOKE/Fumes checklist in order to be ready to run the checklist if the Captain called for it. As a crew we determined the quickest and safest response was to immediately return to the gate in order to open the door and deplane the crew and passengers. We did that and were back at the gate at XA:47z. We subsequently began running the checklist provided in the FOM. Subsequent to our return the two flight attendants in the forward part of the cabin began feeling ill. They complained of nausea and headaches and the number 1 also said she had a metallic taste in her mouth. They eventually sought medical attention. I am not aware of any passengers that sought medical attention. The Captain and I never got sick and we never smelled any odor that seemed suspicious; foul; concerning; unsafe; or abnormal to us. It is my belief that 'possible' odor event was actually a smell coming from the ovens and was not unsafe or unusual. Not sure. Perhaps not using the ovens on the ground or at the beginning of the flight before becoming airborne?
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.