 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Pilot read back wrong assigned altitude even though it was inappropriate to the direction of flight. Controller did not correct it. TCASII and controller caught altitude deviation and traffic conflict at about the same time.
| Attributes | |
| ACN | 441153 |
| Time | |
| Date | 199906 |
| Day | Fri |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | navaid : put.vortac |
| State Reference | CT |
| Altitude | msl bound lower : 26000 msl bound upper : 26600 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zbw.artcc |
| Operator | general aviation : corporate |
| Make Model Name | Cessna Citation Undifferentiated or Other Model |
| Operating Under FAR Part | Part 91 |
| Flight Phase | climbout : intermediate altitude |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : corporate |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : commercial pilot : instrument pilot : multi engine |
| Experience | flight time last 90 days : 95 flight time total : 22000 |
| ASRS Report | 441153 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Events | |
| Anomaly | altitude deviation : overshoot conflict : airborne less severe non adherence : clearance |
| Independent Detector | aircraft equipment : tcas other controllera |
| Resolutory Action | controller : separated traffic flight crew : returned to assigned altitude flight crew : took precautionary avoidance action |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance ATC Human Performance |
| Primary Problem | Flight Crew Human Performance |
Narrative:
We departed bed as aircraft X. Because of the unusual call sign, I was listening carefully to the radio. After being switched to ZBW, we were told to climb to and maintain FL270, and I read back 'cleared to FL270.' as we reached FL266, the TCASII alert went off and center called at exactly the same time to ask our altitude. He said he cleared us to FL260. I heard and read back FL270, which was not corrected by ATC. Fortunately, there was no harm to anyone. 2 comments: 1) the frequency was very congested and I was not able to call back and verify the altitude since it was not appropriate for my direction of flight. 2) the pilot rumor mill is saying that controllers are no longer responsible for correcting readback errors made by a pilot. If this is true, what is the purpose of the readback?
Original NASA ASRS Text
Title: PLT READ BACK WRONG ASSIGNED ALT EVEN THOUGH IT WAS INAPPROPRIATE TO THE DIRECTION OF FLT. CTLR DID NOT CORRECT IT. TCASII AND CTLR CAUGHT ALTDEV AND TFC CONFLICT AT ABOUT THE SAME TIME.
Narrative: WE DEPARTED BED AS ACFT X. BECAUSE OF THE UNUSUAL CALL SIGN, I WAS LISTENING CAREFULLY TO THE RADIO. AFTER BEING SWITCHED TO ZBW, WE WERE TOLD TO CLB TO AND MAINTAIN FL270, AND I READ BACK 'CLRED TO FL270.' AS WE REACHED FL266, THE TCASII ALERT WENT OFF AND CTR CALLED AT EXACTLY THE SAME TIME TO ASK OUR ALT. HE SAID HE CLRED US TO FL260. I HEARD AND READ BACK FL270, WHICH WAS NOT CORRECTED BY ATC. FORTUNATELY, THERE WAS NO HARM TO ANYONE. 2 COMMENTS: 1) THE FREQ WAS VERY CONGESTED AND I WAS NOT ABLE TO CALL BACK AND VERIFY THE ALT SINCE IT WAS NOT APPROPRIATE FOR MY DIRECTION OF FLT. 2) THE PLT RUMOR MILL IS SAYING THAT CTLRS ARE NO LONGER RESPONSIBLE FOR CORRECTING READBACK ERRORS MADE BY A PLT. IF THIS IS TRUE, WHAT IS THE PURPOSE OF THE READBACK?
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.