37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1466735 |
Time | |
Date | 201707 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | B767 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
Component | |
Aircraft Component | Navigational Equipment and Processing |
Person 1 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Pilot Flying Captain |
Events | |
Anomaly | Aircraft Equipment Problem Critical Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor |
Narrative:
As a brief history; on our flight the day before on [this aircraft]; upon landing an electrical burning smell was present in the flight deck. The mechanic who was riding with us said that he had been on the aircraft previously and the crew noted the same smell on a prior flight. After block-in; we wrote up the smell in the logbook and it was checked by maintenance. Regarding this flight; loading; push; taxi; and takeoff were uneventful. Captain (ca) was pilot flying (PF) and I was pilot monitoring (pm). Upon reaching 11;000 feet; we detected the same electrical odor again. The ca's mfd began to cycle on and off with an associated clicking sound. After approximately a dozen cycles; the CRT screen made a loud 'pop' and went blank. The burning smell increased at that time. We asked the mechanic to pull the circuit break (circuit breaker) for that screen in the interest of safety and he found it had popped on its own. We requested a level off at 16;000 feet and slowed to 250 KIAS in preparation for return. After discussing the matter we agreed that it would be prudent to return and the captian requested the smoke; fire; fumes QRH. We informed center and were vectored back to the airport. On base; the first officer's FMS CDU display showed a few random characters on the screen and then went completely blank. After turning off the runway; the lower EICAS screen went blank as well. The mechanic pulled the circuit breaker's for those two screens. We taxied to the north ramp without further incident. Talking with other pilots that have flown this particular airframe; it seems to have a distinct history of these types of failures in recent weeks. Several entries in the logbook confirm that. The cause for these failures needs to be definitively identified and fixed.
Original NASA ASRS Text
Title: B767 flight crew experienced an electrical burning odor on departure and elected to return to the departure airport. The Captain's MFD went blank; soon after the First Officer FMS and CDU display went blank. After landing the lower EICAS screen went blank as well.
Narrative: As a brief history; on our flight the day before on [this aircraft]; upon landing an electrical burning smell was present in the flight deck. The mechanic who was riding with us said that he had been on the aircraft previously and the crew noted the same smell on a prior flight. After block-in; we wrote up the smell in the logbook and it was checked by maintenance. Regarding this flight; loading; push; taxi; and takeoff were uneventful. Captain (CA) was Pilot Flying (PF) and I was Pilot Monitoring (PM). Upon reaching 11;000 feet; we detected the same electrical odor again. The CA's MFD began to cycle on and off with an associated clicking sound. After approximately a dozen cycles; the CRT screen made a loud 'pop' and went blank. The burning smell increased at that time. We asked the mechanic to pull the Circuit Break (CB) for that screen in the interest of safety and he found it had popped on its own. We requested a level off at 16;000 feet and slowed to 250 KIAS in preparation for return. After discussing the matter we agreed that it would be prudent to return and the Captian requested the Smoke; Fire; Fumes QRH. We informed Center and were vectored back to the airport. On base; the First Officer's FMS CDU display showed a few random characters on the screen and then went completely blank. After turning off the runway; the lower EICAS screen went blank as well. The mechanic pulled the CB's for those two screens. We taxied to the north ramp without further incident. Talking with other pilots that have flown this particular airframe; it seems to have a distinct history of these types of failures in recent weeks. Several entries in the logbook confirm that. The cause for these failures needs to be definitively identified and fixed.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.