37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 630777 |
Time | |
Date | 200409 |
Day | Mon |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : atl.airport |
State Reference | GA |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Regional Jet 200 ER&LR |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Experience | flight time last 90 days : 240 flight time total : 4000 flight time type : 1850 |
ASRS Report | 630777 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Experience | flight time last 90 days : 200 flight time total : 10200 flight time type : 6800 |
ASRS Report | 630452 |
Events | |
Anomaly | aircraft equipment problem : less severe |
Independent Detector | aircraft equipment other aircraft equipment : efis warning hdg other flight crewa other flight crewb |
Supplementary | |
Problem Areas | FAA Aircraft Flight Crew Human Performance |
Primary Problem | Aircraft |
Narrative:
While taxiing out to runway 8R in atlanta, the EFIS computer monitor message (heading) appeared. The message was cleared. The message then returned and cleared itself. After takeoff, the message appeared again. At this point, the QRH was completed and the message cleared and did not return for the remainder of the flight. On the flight was an FAA inspector who was in the jump seat and asked questions regarding the procedure and if we were going to make a write-up of the discrepancy. Upon landing, the captain made the write-up and maintenance met the plane. Supplemental information from acn 630452: an FAA inspector on the jumpseat of the FAA national simulator program did not seem comfortable about such EFIS anomalies related to ground interferences and felt we should have done the QRH procedure and called dispatch and maintenance. I explained about lga on runway 13 even having to select 'de' mode sometimes because of interferences and he still did not seem satisfied about such anomalies.
Original NASA ASRS Text
Title: CRJ200 CREW HAD THE EFIS COMPUTER 'MONITOR HDG' CAUTION MESSAGE COME ON.
Narrative: WHILE TAXIING OUT TO RWY 8R IN ATLANTA, THE EFIS COMPUTER MONITOR MESSAGE (HDG) APPEARED. THE MESSAGE WAS CLRED. THE MESSAGE THEN RETURNED AND CLRED ITSELF. AFTER TKOF, THE MESSAGE APPEARED AGAIN. AT THIS POINT, THE QRH WAS COMPLETED AND THE MESSAGE CLRED AND DID NOT RETURN FOR THE REMAINDER OF THE FLT. ON THE FLT WAS AN FAA INSPECTOR WHO WAS IN THE JUMP SEAT AND ASKED QUESTIONS REGARDING THE PROC AND IF WE WERE GOING TO MAKE A WRITE-UP OF THE DISCREPANCY. UPON LNDG, THE CAPT MADE THE WRITE-UP AND MAINT MET THE PLANE. SUPPLEMENTAL INFO FROM ACN 630452: AN FAA INSPECTOR ON THE JUMPSEAT OF THE FAA NATIONAL SIMULATOR PROGRAM DID NOT SEEM COMFORTABLE ABOUT SUCH EFIS ANOMALIES RELATED TO GND INTERFERENCES AND FELT WE SHOULD HAVE DONE THE QRH PROC AND CALLED DISPATCH AND MAINT. I EXPLAINED ABOUT LGA ON RWY 13 EVEN HAVING TO SELECT 'DE' MODE SOMETIMES BECAUSE OF INTERFERENCES AND HE STILL DID NOT SEEM SATISFIED ABOUT SUCH ANOMALIES.
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.