37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1717109 |
Time | |
Date | 202001 |
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 | EMB ERJ 145 ER/LR |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb Takeoff |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine Flight Crew Instrument |
Events | |
Anomaly | Aircraft Equipment Problem Critical Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor |
Narrative:
Shortly after takeoff while on initial climb out we received a triple chime and an EICAS 'lav smoke' warning. This occurred at approximately 500 ft. Within a few seconds the flight attendant called the captain and alerted us to the presence of smoke in the cabin. The captain ran the QRH; contacted departure and [requested priority handling]. We were vectored back for the landing with [ground] equipment on standby. Landing was routine and we taxied back to the gate without further incident.the main thing I learned from this event is that remaining calm and continuing to perform as a crew using threat and error management and CRM can prevent things from becoming much worse. I and the captain both remained calm; followed procedure; and continued as normally as possible. I will use this experience when I become a captain to instill in my first officers the importance of remaining calm and following procedure.
Original NASA ASRS Text
Title: An Air Carrier pilot reported returning to the airport due to smoke in the cabin and a LAV SMOKE alert.
Narrative: Shortly after takeoff while on initial climb out we received a triple chime and an EICAS 'LAV SMOKE' warning. This occurred at approximately 500 ft. Within a few seconds the Flight Attendant called the Captain and alerted us to the presence of smoke in the cabin. The Captain ran the QRH; contacted Departure and [requested priority handling]. We were vectored back for the landing with [ground] equipment on standby. Landing was routine and we taxied back to the gate without further incident.The main thing I learned from this event is that remaining calm and continuing to perform as a crew using threat and error management and CRM can prevent things from becoming much worse. I and the Captain both remained calm; followed procedure; and continued as normally as possible. I will use this experience when I become a Captain to instill in my First Officers the importance of remaining calm and following procedure.
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.