 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Flight crew of air carrier medium large transport were advised by ATC that the altitude readout showed the aircraft overshot cruise altitude.
| Attributes | |
| ACN | 274729 |
| Time | |
| Date | 199406 |
| Day | Fri |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | atc facility : syr |
| State Reference | NY |
| Altitude | msl bound lower : 29000 msl bound upper : 29000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zob |
| Operator | common carrier : air carrier |
| Make Model Name | DC-9 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | cruise other |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : flight engineer pilot : atp pilot : commercial |
| Experience | flight time last 90 days : 230 flight time total : 8400 |
| ASRS Report | 274729 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Events | |
| Anomaly | aircraft equipment problem : less severe altitude deviation : overshoot non adherence : clearance other anomaly other |
| Independent Detector | atc equipment other atc equipment : unspecified other controllera |
| Resolutory Action | flight crew : overcame equipment problem |
| Consequence | faa : reviewed incident with flight crew |
| Supplementary | |
| Primary Problem | Aircraft |
| Air Traffic Incident | other |
Narrative:
On flight from dtw to syr captain flying leveled off at 29000 ft. After about 5 mins ATC asked us our altitude. I responded level '290.' we verified our altimeters at 29.92 inches. Captain altitude showed 29000 ft. First officer's showed 28800 well within tolerances. After a long silence I asked ATC what the problem was and if he needed us at a different altitude. He said no, but his radar showed us 500 ft high for a brief moment. After that nothing was said and we surmised it must have been his equipment and not ours since earlier and later no controller noticed anything wrong with our altitude readout. On our return flight we wrote up the #1 transponder mode-C as a precaution. In this event we did nothing out of the norm. However, in similar cases we have heard of FAA enforcement action against a crew with a transponder malfunction during the cruise phase of a flight.
Original NASA ASRS Text
Title: FLC OF ACR MLG WERE ADVISED BY ATC THAT THE ALT READOUT SHOWED THE ACFT OVERSHOT CRUISE ALT.
Narrative: ON FLT FROM DTW TO SYR CAPT FLYING LEVELED OFF AT 29000 FT. AFTER ABOUT 5 MINS ATC ASKED US OUR ALT. I RESPONDED LEVEL '290.' WE VERIFIED OUR ALTIMETERS AT 29.92 INCHES. CAPT ALT SHOWED 29000 FT. FO'S SHOWED 28800 WELL WITHIN TOLERANCES. AFTER A LONG SILENCE I ASKED ATC WHAT THE PROB WAS AND IF HE NEEDED US AT A DIFFERENT ALT. HE SAID NO, BUT HIS RADAR SHOWED US 500 FT HIGH FOR A BRIEF MOMENT. AFTER THAT NOTHING WAS SAID AND WE SURMISED IT MUST HAVE BEEN HIS EQUIP AND NOT OURS SINCE EARLIER AND LATER NO CTLR NOTICED ANYTHING WRONG WITH OUR ALT READOUT. ON OUR RETURN FLT WE WROTE UP THE #1 XPONDER MODE-C AS A PRECAUTION. IN THIS EVENT WE DID NOTHING OUT OF THE NORM. HOWEVER, IN SIMILAR CASES WE HAVE HEARD OF FAA ENFORCEMENT ACTION AGAINST A CREW WITH A XPONDER MALFUNCTION DURING THE CRUISE PHASE OF A FLT.
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.