2025-02 · NASA ASRS report 2210149
B737-800 flight crew and flight attendants reported a fumes event during climb. The flight crew diverted and landed safely.
During climb; some time prior to reaching cruise altitude; strong smoky strange odor present in flight deck and cabin. I contacted the Purser to determine if she was heating first class meals. When asked if she could smell the odor; she stated that she had turned off the oven and that she was going to try to use the other oven. After a few minutes I called again due to the fact that the odor persisted in the flight deck. The Purser stated the odor persisted also in the cabin; but couldn't identify the source of the odor and no smoke was observed.While talking with the aft cabin flight attendants I was informed that they could smell the odor and they believed it was a bit 'hazy'; also that one or both of the aft flight attendants were feeling ill and nauseous and that a passenger was feeling well. At this point we [requested priority handling] with ATC and diverted to ZZZ. I performed the QRC for Smoke; fire; or fumes which led to the QRH; then the descent and before landing checklists were completed and proceeded to land safely.Cause: At this point I'm not aware of the cause or source of the odor.
During climb around 28;000; myself; the Captain; and our jumpseater all noticed a strong burning oil odor. The Captain called the Purser to ask if she noticed any strange smells. She did and first suspected it was an oven. She turned off that oven and used the other. The smell got worse for both the cockpit and cabin. The Purser called up again to say the ovens are now off but the odor is much worse and there's a slight haze in the cabin. She also said that some first-class passengers were complaining about the odor. Engine instruments; performance; and pressurization were normal. The Captain started running the QRC and then QRH for smoke fire fumes. We donned oxygen per the checklist; [requested priority handling]; and proceeded to ZZZ to get on the ground quickly since we could not locate the source of the burning odor. According to the FA's (Flight Attendant) the smell persisted despite the checklist being completed. We deployed the cabin masks as a precaution so the PAX (Passengers) and FAs didn't have to breathe the toxic fumes. I maintained about 330-320kts until about 5000' then slowed and configured for an uneventful; but overweight landing. Upon deplaning at the gate one FA vomited and was treated by EMS. Another said she was very close to vomiting as well. Cause: I pulled the logbook a few hours later to my disappointment saw the fume event was signed off with oven replacements. The smell was not a hot or burning oven. The smell was not deice fluid either like MX (Maintenance) suggested when we first blocked in. Those both have distinct smells and this wasn't it. The smell was burning/hot oil of some kind.
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.