<< >> NASA ASRS Report 402287, May 1998

Mdt aircraft in approach phase had APU fire warning after starting it. Flight crew followed emergency procedures, shut down APU, declared emergency, and landed uneventfully. Postflt inspection showed no indication of fire.

Attributes
ACN	402287
Time
Date	199805
Day	Sat
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : dsm
State Reference	IA
Altitude	msl bound lower : 2500 msl bound upper : 2500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : dsm
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	descent : approach landing other other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 240 flight time total : 9000 flight time type : 2000
ASRS Report	402287
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 230 flight time total : 4200 flight time type : 230
ASRS Report	403096
Events
Anomaly	aircraft equipment problem : critical other anomaly other
Independent Detector	aircraft equipment other aircraft equipment : unspecified
Resolutory Action	flight crew : declared emergency none taken : unable
Consequence	Other
Supplementary
Primary Problem	Aircraft

Narrative:

During approach phase of flight, the APU was started. After completion of APU start cycle, we had an indication of an APU fire. We followed procedure for an APU fire and secured the APU, declared an emergency, and landed in dsm. No evacuate/evacuation occurred as APU fire indication went out after using the APU fire bottle. Subsequent landing was normal. After inspection of the aircraft found no apparent indication of fire. Aircraft was inspected by maintenance and they concurred there was no indication of actual fire. Maintenance discrepancy entered in logbook.

Related reports:

• MD83 first officer experiences an IRU fault during cruise wh...
• CRJ200 first officer experiences a flaps fail message; when ...
• A B737-800 flight crew executed a go-around; performed the a...
• A B767-200ER flight crew abandoned their approach upon recei...
• A CRJ700 on approach at 8000 ft declared an emergency due to...
• A320 flight crew has a hydraulic Y system malfunction; perfo...

	Enter your search terms Submit search form
	Web www.37000feet.com

Original NASA ASRS Text

Title: MDT ACFT IN APCH PHASE HAD APU FIRE WARNING AFTER STARTING IT. FLC FOLLOWED EMER PROCS, SHUT DOWN APU, DECLARED EMER, AND LANDED UNEVENTFULLY. POSTFLT INSPECTION SHOWED NO INDICATION OF FIRE.

Narrative: DURING APCH PHASE OF FLT, THE APU WAS STARTED. AFTER COMPLETION OF APU START CYCLE, WE HAD AN INDICATION OF AN APU FIRE. WE FOLLOWED PROC FOR AN APU FIRE AND SECURED THE APU, DECLARED AN EMER, AND LANDED IN DSM. NO EVAC OCCURRED AS APU FIRE INDICATION WENT OUT AFTER USING THE APU FIRE BOTTLE. SUBSEQUENT LNDG WAS NORMAL. AFTER INSPECTION OF THE ACFT FOUND NO APPARENT INDICATION OF FIRE. ACFT WAS INSPECTED BY MAINT AND THEY CONCURRED THERE WAS NO INDICATION OF ACTUAL FIRE. MAINT DISCREPANCY ENTERED IN LOGBOOK.

Data retrieved from NASA's ASRS site as of July 2007 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.