2024-05 · NASA ASRS report 2115697
Air carrier flight crew and Flight Attendant reported a fumes event during cruise on the flight deck. The flight crew completed the appropriate QRH procedures and requested priority handling to a suitable diversion airport where the aircraft was removed from service.
Our flight was established at cruise at FL300 while transiting over the ocean. The CA was the PF; the FO was the PM. For a period of 30-40 minutes prior to the event; there was discussion by the CA regarding an unusual smell; similar to an ozone odor or slightly electrical smell. A brief investigation of the flight deck revealed no source of the slight odor but it was persistent. As a precaution; several divert fields were reviewed along the route (ZZZ; ZZZ1; ZZZ2) in case the odor became significant or the event elevated. During the crew meal service; the PM asked the FA's (Flight Attendants) if they smelled anything unusual in the cabin of which the reply was negative. However; the FA did detect an odor while the flight deck door was opened emitting from the flight deck. At approximately XA25; an obvious plume of smoke was visible emitting from the CA side of the center console. The crew donned their oxygen masks and they remained on for the duration of the diversion. Aircraft control was stated by the PF and the non-normal methodology was employed. Using the QRC initially; the AVIONICS SMOKE procedure was employed. Following the checklist; aircraft control was transferred to the FO (now the PF) and the CA proceeded to continue the checklist; notify dispatch (ACARS transponder XXXX message); brief the cabin crew using the precautionary landing items and brief the passengers on the pending diversion. Following these items; a review of the non-routine landing checklist was completed. The aircraft was below its maximum landing weight. During the PM duties by the CA; the PF completed the notification with ATC and briefed our intent to divert; discussed divert airfield options; weather; approach and runway in use. As available; the PM assisted with FMS management; approach review and landing preferences with the PF. An uneventful landing was completed at ZZZ [airport] on runway XX. ARFF (Airport Rescue and Firefighting) was not visible on landing; but after the aircraft taxied to gate A; ARFF crew visited the flight deck and did a thermal/heat signature review of the flight deck for any possible hidden fire under the center console since it was still smoldering. Maintenance then removed the radar control panel; which continued to smolder as it was removed from the aircraft. All passengers safely deplaned via the main cabin door. The aircraft was removed from service. AML (Aircraft Maintenance Logbook) entries were completed for the radar control panel and the depletion of the crew oxygen bottle. The crew was placed into a rest period since the cockpit crew would soon time out of the FDP (Flight Duty Period). A report was completed for multiple items: diversion; smoke event and [requesting priority handling]; as well as for the Smoke and Fume event. Additionally; a post-flight phone call to dispatch and the Chief Pilot was completed. Cause: Aged or broken wiring within the radar control panel. No visible scoring or burn marks on the exterior of the metal box. The cannon-plug looked intact on post-flight inspection with maintenance.
While in cruise the CA noticed a slight odor and described it as smelling like ozone; I could smell it faintly as well. Shortly after we both saw a burst of light blue/gray colored smoke come from somewhere out of the CA's side of the center console; it dissipated rapidly. The CA called for the quick action items for 'smoke' which were completed along with the QRH actions. We [advised ATC] and requested a diversion. The CA assigned me to assume the PF duties and we proceeded to ZZZ and landed without further incident. Cause: Failure of an electrical component. After landing and deplaning while conferring with maintenance we were able to observe a trace of smoke continuing to be emitted from the weather radar control panel. Maintenance removed it from the aircraft. Suggestions: Examination of the failed component to identify the cause.
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.