37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1352879 |
Time | |
Date | 201605 |
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 | B737-700 |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
Person 1 | |
Function | Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 237 |
Person 2 | |
Function | First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 239 |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe |
Narrative:
During preflight of the cargo fire panel; the 'disch' light did not illuminate. It also did not illuminate with the master light test switch. Dispatch; maintenance and contract maintenance were notified. During troubleshooting; the 'aft ext' light stopped testing correctly and the 'aft' fire alert illuminated accompanied by the fire bell. The alert occurred several times. The aircraft was subsequently returned to service per mels which required maintenance action. Shortly after takeoff; the 'aft' cargo fire alerted accompanied by the fire bell. The alert/bell lasted approximately five seconds. The QRH was referenced. Due to the previous maintenance on the control panel and the fact that the indications had returned to normal; the fire bottle was not discharged. [ATC was advised]; the flight attendants and passengers were briefed; rescue support was requested; and [company] was advised of our return. After landing; the runway was cleared; APU was started; and engine number two was shutdown to allow fire crew access to the aft of the aircraft. No abnormalities were noted by the fire crew; and we continued to the gate. After parking procedures were accomplished; I inspected the aft cargo bin; which was empty. However; the ramp agent who opened the cargo bin reported 'smoke' when he first opened the hatch. The fire crew inspected the bin and found no heat sources or fire indications. Contract maintenance inspected the bin and found nothing conclusive.the passengers seemed in good spirits during deplaning. The flight attendants were debriefed; and also seemed fine. Dispatch; company maintenance; and the chief pilot on call were all contacted. An entry was made in the aircraft logbook. All crew members and support operations functioned well. However; during my post event duties; I was interrupted several times by phone calls. It is imperative that post event actions be handled correctly; to include interfacing with the passengers and crew and possibly the agents; maintenance and fire crew. I understand the perceived needs of other offices to contact the crew but this must not interfere with the crew's performance of their duties.equipment malfunctions will always occur. However; our post event procedures can be improved to include a single point of contact for the crew. As I understand my responsibilities; I must contact dispatch; maintenance; and scheduling. A call to the chief pilot on call is desirable. A call to [the pilots' union] might also be warranted. A single point of contact could greatly streamline these responsibilities and eliminate some errors.
Original NASA ASRS Text
Title: B737-700 flight crew reported returning to departure airport after receiving an Aft Cargo Fire warning that turned out to be an apparent false warning.
Narrative: During preflight of the Cargo Fire panel; the 'DISCH' light did not illuminate. It also did not illuminate with the Master Light test switch. Dispatch; Maintenance and Contract Maintenance were notified. During troubleshooting; the 'AFT EXT' light stopped testing correctly and the 'AFT' Fire Alert illuminated accompanied by the fire bell. The alert occurred several times. The aircraft was subsequently returned to service per MELs which required Maintenance action. Shortly after takeoff; the 'AFT' Cargo Fire alerted accompanied by the fire bell. The alert/bell lasted approximately five seconds. The QRH was referenced. Due to the previous Maintenance on the control panel and the fact that the indications had returned to normal; the fire bottle was not discharged. [ATC was advised]; the Flight Attendants and Passengers were briefed; rescue support was requested; and [company] was advised of our return. After landing; the runway was cleared; APU was started; and engine number two was shutdown to allow Fire Crew access to the aft of the aircraft. No abnormalities were noted by the Fire Crew; and we continued to the gate. After parking procedures were accomplished; I inspected the aft cargo bin; which was empty. However; the Ramp Agent who opened the cargo bin reported 'smoke' when he first opened the hatch. The fire crew inspected the bin and found no heat sources or fire indications. Contract Maintenance inspected the bin and found nothing conclusive.The passengers seemed in good spirits during deplaning. The Flight Attendants were debriefed; and also seemed fine. Dispatch; Company Maintenance; and the Chief Pilot on Call were all contacted. An entry was made in the aircraft logbook. All crew members and support operations functioned well. However; during my post event duties; I was interrupted several times by phone calls. It is imperative that post event actions be handled correctly; to include interfacing with the passengers and crew and possibly the agents; Maintenance and Fire Crew. I understand the perceived needs of other offices to contact the crew but this must not interfere with the crew's performance of their duties.Equipment malfunctions will always occur. However; our post event procedures can be improved to include a single point of contact for the Crew. As I understand my responsibilities; I must contact Dispatch; Maintenance; and Scheduling. A call to the Chief Pilot on Call is desirable. A call to [the pilots' union] might also be warranted. A single point of contact could greatly streamline these responsibilities and eliminate some errors.
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.