37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 245972 |
Time | |
Date | 199307 |
Day | Sat |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : pcu |
State Reference | MS |
Altitude | msl bound lower : 3000 msl bound upper : 5000 |
Environment | |
Flight Conditions | Mixed |
Light | Daylight |
Aircraft 1 | |
Operator | general aviation : instructional |
Make Model Name | Small Aircraft, Low Wing, 1 Eng, Retractable Gear |
Flight Phase | cruise other descent other |
Route In Use | enroute : direct enroute airway : msy |
Flight Plan | IFR |
Aircraft 2 | |
Operator | general aviation : instructional |
Make Model Name | Small Aircraft |
Flight Phase | cruise other |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : instrument pilot : cfi pilot : commercial |
Experience | flight time last 90 days : 30 flight time total : 1000 flight time type : 40 |
ASRS Report | 245972 |
Person 2 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : commercial pilot : instrument |
Events | |
Anomaly | altitude deviation : excursion from assigned altitude non adherence : clearance non adherence : published procedure other anomaly other |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance flight crew : returned to intended course or assigned course other |
Consequence | Other |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | other |
Narrative:
IFR flight omn-aus. This leg was omn 0r9 (hammond municipal) for a fuel stop. Traveling west on V-70 we were approximately 5 mi north of course due to a deviation around a cumulus buildup, we were cleared direct hammond VOR. Then we were given vectors to intercept V-70. The reason for this apparently was for spacing from aircraft Y who was inbound to 0r9. The problem occurred because our call sign was abxyz and the other aircraft's was cdxyz. We were at 5000 ft MSL approximately 20 mi out from hammond on the vector when I requested a descent to 3000 ft. A few seconds later the controller cleared xyz to 3000 ft and I acknowledged the clearance out of 5000 ft for 3000 ft. Apparently the descent was meant for aircraft Y (who was not descending), although he must have thought it was for me (as I did) or he would have acknowledged the descent clearance. While I was descending through about 4300 ft MSL the controller called and said we were supposed to be at 5000 ft. He issued us an immediate climb to 5000 ft (and a vector, I think) and an immediate descent to 3000 ft for the other aircraft. We never saw the other aircraft but I don't think we came within 3-4 mi of its position due to IFR separation. The remainder of the flight was uneventful. The controller used both aircraft's full call signs from this point on, and emphasized the first 2 numbers to assure there was no doubt who his instructions were for. I spoke with the pilot of aircraft Y on the ground at hammond and discovered he was continuing west on the same route as I was planning, so I waited about a half hour after he departed before I left so a similar problem wouldn't occur. I think the problem occurred because you become attuned to hearing your call (xyz in this case) and focus your attention on it, any distraction and you can miss the first part of the call sign because by habit your ears aren't trained to listen to anything but the last 3 numbers (letters). I don't remember if the controller was using our full call signs at this point. Since I had requested the descent to 3000 ft, when the controller cleared 'xyz' to 3000 ft I thought it was my clearance. One inaction on my part I regret was in not querying the controller about the descent. He gave us a new vector as we were descending, and as I acknowledged the turn, I wanted to ask him to verify that we were cleared to 3000 ft but I never got the words out. Lesson: when in doubt, no matter how small, don't be afraid to ask for clarification!
Original NASA ASRS Text
Title: ALTDEV ALT EXCURSION DUE TO REPLY TO WRONG CALL SIGN INCOMPLETE CALL SIGN. SIMILAR A/N.
Narrative: IFR FLT OMN-AUS. THIS LEG WAS OMN 0R9 (HAMMOND MUNICIPAL) FOR A FUEL STOP. TRAVELING W ON V-70 WE WERE APPROX 5 MI N OF COURSE DUE TO A DEV AROUND A CUMULUS BUILDUP, WE WERE CLRED DIRECT HAMMOND VOR. THEN WE WERE GIVEN VECTORS TO INTERCEPT V-70. THE REASON FOR THIS APPARENTLY WAS FOR SPACING FROM ACFT Y WHO WAS INBOUND TO 0R9. THE PROB OCCURRED BECAUSE OUR CALL SIGN WAS ABXYZ AND THE OTHER ACFT'S WAS CDXYZ. WE WERE AT 5000 FT MSL APPROX 20 MI OUT FROM HAMMOND ON THE VECTOR WHEN I REQUESTED A DSCNT TO 3000 FT. A FEW SECONDS LATER THE CTLR CLRED XYZ TO 3000 FT AND I ACKNOWLEDGED THE CLRNC OUT OF 5000 FT FOR 3000 FT. APPARENTLY THE DSCNT WAS MEANT FOR ACFT Y (WHO WAS NOT DSNDING), ALTHOUGH HE MUST HAVE THOUGHT IT WAS FOR ME (AS I DID) OR HE WOULD HAVE ACKNOWLEDGED THE DSCNT CLRNC. WHILE I WAS DSNDING THROUGH ABOUT 4300 FT MSL THE CTLR CALLED AND SAID WE WERE SUPPOSED TO BE AT 5000 FT. HE ISSUED US AN IMMEDIATE CLB TO 5000 FT (AND A VECTOR, I THINK) AND AN IMMEDIATE DSCNT TO 3000 FT FOR THE OTHER ACFT. WE NEVER SAW THE OTHER ACFT BUT I DON'T THINK WE CAME WITHIN 3-4 MI OF ITS POS DUE TO IFR SEPARATION. THE REMAINDER OF THE FLT WAS UNEVENTFUL. THE CTLR USED BOTH ACFT'S FULL CALL SIGNS FROM THIS POINT ON, AND EMPHASIZED THE FIRST 2 NUMBERS TO ASSURE THERE WAS NO DOUBT WHO HIS INSTRUCTIONS WERE FOR. I SPOKE WITH THE PLT OF ACFT Y ON THE GND AT HAMMOND AND DISCOVERED HE WAS CONTINUING W ON THE SAME RTE AS I WAS PLANNING, SO I WAITED ABOUT A HALF HR AFTER HE DEPARTED BEFORE I LEFT SO A SIMILAR PROB WOULDN'T OCCUR. I THINK THE PROB OCCURRED BECAUSE YOU BECOME ATTUNED TO HEARING YOUR CALL (XYZ IN THIS CASE) AND FOCUS YOUR ATTN ON IT, ANY DISTR AND YOU CAN MISS THE FIRST PART OF THE CALL SIGN BECAUSE BY HABIT YOUR EARS AREN'T TRAINED TO LISTEN TO ANYTHING BUT THE LAST 3 NUMBERS (LETTERS). I DON'T REMEMBER IF THE CTLR WAS USING OUR FULL CALL SIGNS AT THIS POINT. SINCE I HAD REQUESTED THE DSCNT TO 3000 FT, WHEN THE CTLR CLRED 'XYZ' TO 3000 FT I THOUGHT IT WAS MY CLRNC. ONE INACTION ON MY PART I REGRET WAS IN NOT QUERYING THE CTLR ABOUT THE DSCNT. HE GAVE US A NEW VECTOR AS WE WERE DSNDING, AND AS I ACKNOWLEDGED THE TURN, I WANTED TO ASK HIM TO VERIFY THAT WE WERE CLRED TO 3000 FT BUT I NEVER GOT THE WORDS OUT. LESSON: WHEN IN DOUBT, NO MATTER HOW SMALL, DON'T BE AFRAID TO ASK FOR CLARIFICATION!
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.