37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1331025 |
Time | |
Date | 201410 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | MD-80 Series (DC-9-80) Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor |
Narrative:
After departure at approximately 4000 MSL I heard the lavatory smoke alarm going off through the closed door. Shortly thereafter the lead flight attendant called up and said that they had an aft lav smoke alarm on both sides. As the nfp I [advised] ATC and requested to return back to the field. Then I grabbed the eqrh (emergency quick reference handbook). The ca then confirmed that he had the plane and the radios and instructed me to run the eqrh checklist. I ran checklist for the lavatory smoke alarm. After I completed the checklist I returned to my duties as nfp ran the descent/approach/landing checklist and we landed uneventfully. The ca decided to return to the gate for deplaning since the flight attendant's could not verify a fire and an evacuation on the runway might have caused more injuries than deplaning at the gate. I agreed with that assessment. Mechanical malfunctions happen so there is not much that can be done preemptively to avoid that. What caused the lav smoke alarm to go off is presently unclear. The flight attendant's and some passenger confirmed that they saw smoke/haze in the area concerned; yet an active fire could not be confirmed. Also; it did not get worse; but rather dissipated slowly. The lav smoke alarm remained on until we got to the gate though. I applaud the flight attendant's for staying calm and relaying that to the passengers. As far as I know no injuries were reported. What I am a little concerned about is the eqrh checklist that deals with the lavatory smoke alarm. It directs the crew to pull a lot of circuit breaker's. Those circuit breaker's are located behind the captain's seat. I could not reach those breakers from my seat (due to phase of flight and impending landing); so the ca had to pull them; despite him being the PF and operating the radios. For this checklist it would be better to have the controls transferred to the first officer so that the ca can locate and pull the cbs without having to fly and call at the same time. In addition; the checklist directed us to pull cbs for the call system. I do not know how that circuit breaker interacts with the lavatory smoke alarm; but what it did do is disable our communication with the flight attendant's as our call-button was rendered inop after pulling that breaker. All communication with the flight attendant's was done by knocking and yelling through the door once [the cbs] were pulled. Though possible; it was not the best solution. But since it was part of the checklist we did not undo that step.
Original NASA ASRS Text
Title: MD-80 First Officer reported returning to departure airport after receiving a lavatory smoke alarm.
Narrative: After departure at approximately 4000 MSL I heard the Lavatory Smoke Alarm going off through the closed door. Shortly thereafter the Lead FA called up and said that they had an Aft Lav Smoke Alarm on both sides. As the NFP I [advised] ATC and requested to return back to the field. Then I grabbed the EQRH (Emergency Quick Reference Handbook). The CA then confirmed that he had the plane and the radios and instructed me to run the EQRH checklist. I ran checklist for the Lavatory Smoke Alarm. After I completed the checklist I returned to my duties as NFP ran the descent/approach/landing checklist and we landed uneventfully. The CA decided to return to the gate for deplaning since the FA's could not verify a fire and an evacuation on the runway might have caused more injuries than deplaning at the gate. I agreed with that assessment. Mechanical malfunctions happen so there is not much that can be done preemptively to avoid that. What caused the Lav Smoke alarm to go off is presently unclear. The FA's and some passenger confirmed that they saw smoke/haze in the area concerned; yet an active fire could not be confirmed. Also; it did not get worse; but rather dissipated slowly. The Lav Smoke alarm remained on until we got to the gate though. I applaud the FA's for staying calm and relaying that to the passengers. As far as I know no injuries were reported. What I am a little concerned about is the EQRH checklist that deals with the Lavatory Smoke Alarm. It directs the crew to pull a lot of CB's. Those CB's are located behind the Captain's seat. I could not reach those breakers from my seat (due to phase of flight and impending landing); so the Ca had to pull them; despite him being the PF and operating the radios. For this checklist it would be better to have the controls transferred to the FO so that the CA can locate and pull the CBs without having to fly and call at the same time. In addition; the checklist directed us to pull CBs for the Call System. I do not know how that CB interacts with the Lavatory Smoke Alarm; but what it did do is disable our communication with the FA's as our call-button was rendered inop after pulling that breaker. All communication with the FA's was done by knocking and yelling through the door once [the CBs] were pulled. Though possible; it was not the best solution. But since it was part of the checklist we did not undo that step.
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.