37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 811438 |
Time | |
Date | 200811 |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | navaid : aml.vortac |
State Reference | VA |
Altitude | msl single value : 4000 |
Environment | |
Flight Conditions | VMC |
Light | Dawn |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | SF 340B |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : approach |
Aircraft 2 | |
Controlling Facilities | tracon : pct.tracon |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Flight Phase | descent : approach |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
ASRS Report | 811438 |
Person 2 | |
Affiliation | government : faa |
Events | |
Anomaly | altitude deviation : excursion from assigned altitude non adherence : clearance other anomaly other |
Independent Detector | other controllera other flight crewa |
Resolutory Action | none taken : detected after the fact |
Supplementary | |
Problem Areas | ATC Human Performance Company Flight Crew Human Performance |
Primary Problem | Company |
Narrative:
We were 30 NM north of iad at 4000 ft on an assigned 200 degree heading with potomac approach. We then received the call 'contact potomac approach.' we checked in on the new frequency at 4000 ft and the controller acknowledged us XXXB. We replied that we were XXXA (we had not yet heard a call for an XXXA and were unaware of their existence to this point). A brief exchange occurred to straighten out our call sign which I believed was due to a typo on our strip. We were then instructed to descend and maintain 3000 ft. Upon reaching approximately 3200 ft; the controller asked if we were about 5 mi north of iad; to which we replied in the negative and that we were at present 25 mi north. The controller then recognized what had happened and we were told that we took our company's call and to go back to our previous frequency. Upon switching back; we heard an XXXB being handed off. When checking back in; we inquired about our altitude; to which we were told was fine. The flight then proceeded as normal until we were once again addressed as XXXB upon exiting runway 1R by the tower controller. (XXXB was at this time parked at the gate.) upon reaching the ramp; we discovered an XXXC also on frequency. After discussing the incident with the crew from XXXB we believe the controller did in fact give instructions that XXXA (not XXXB) was to change frequency by mistake for the crew of XXXB was wondering why they themselves had not been switched yet. XXXB also reported difficulty in communicating with operations; as their calls were repeatedly read back as XXXA. The controller noticed that the aircraft he thought he told to descend was not descending. We followed instructions from ATC. The practice of organizing flight numbers by bank may be convenient from a clerical standpoint; but it is outright dangerous at the operational level.
Original NASA ASRS Text
Title: SF34 EXPERIENCES ALTITUDE EXCURSION AS THE RESULT OF ACCEPTING CLEARANCE FOR ANOTHER FLIGHT WITH A SIMILAR CALL SIGN.
Narrative: WE WERE 30 NM N OF IAD AT 4000 FT ON AN ASSIGNED 200 DEG HDG WITH POTOMAC APCH. WE THEN RECEIVED THE CALL 'CONTACT POTOMAC APCH.' WE CHKED IN ON THE NEW FREQ AT 4000 FT AND THE CTLR ACKNOWLEDGED US XXXB. WE REPLIED THAT WE WERE XXXA (WE HAD NOT YET HEARD A CALL FOR AN XXXA AND WERE UNAWARE OF THEIR EXISTENCE TO THIS POINT). A BRIEF EXCHANGE OCCURRED TO STRAIGHTEN OUT OUR CALL SIGN WHICH I BELIEVED WAS DUE TO A TYPO ON OUR STRIP. WE WERE THEN INSTRUCTED TO DSND AND MAINTAIN 3000 FT. UPON REACHING APPROX 3200 FT; THE CTLR ASKED IF WE WERE ABOUT 5 MI N OF IAD; TO WHICH WE REPLIED IN THE NEGATIVE AND THAT WE WERE AT PRESENT 25 MI N. THE CTLR THEN RECOGNIZED WHAT HAD HAPPENED AND WE WERE TOLD THAT WE TOOK OUR COMPANY'S CALL AND TO GO BACK TO OUR PREVIOUS FREQ. UPON SWITCHING BACK; WE HEARD AN XXXB BEING HANDED OFF. WHEN CHKING BACK IN; WE INQUIRED ABOUT OUR ALT; TO WHICH WE WERE TOLD WAS FINE. THE FLT THEN PROCEEDED AS NORMAL UNTIL WE WERE ONCE AGAIN ADDRESSED AS XXXB UPON EXITING RWY 1R BY THE TWR CTLR. (XXXB WAS AT THIS TIME PARKED AT THE GATE.) UPON REACHING THE RAMP; WE DISCOVERED AN XXXC ALSO ON FREQ. AFTER DISCUSSING THE INCIDENT WITH THE CREW FROM XXXB WE BELIEVE THE CTLR DID IN FACT GIVE INSTRUCTIONS THAT XXXA (NOT XXXB) WAS TO CHANGE FREQ BY MISTAKE FOR THE CREW OF XXXB WAS WONDERING WHY THEY THEMSELVES HAD NOT BEEN SWITCHED YET. XXXB ALSO RPTED DIFFICULTY IN COMMUNICATING WITH OPS; AS THEIR CALLS WERE REPEATEDLY READ BACK AS XXXA. THE CTLR NOTICED THAT THE ACFT HE THOUGHT HE TOLD TO DSND WAS NOT DSNDING. WE FOLLOWED INSTRUCTIONS FROM ATC. THE PRACTICE OF ORGANIZING FLT NUMBERS BY BANK MAY BE CONVENIENT FROM A CLERICAL STANDPOINT; BUT IT IS OUTRIGHT DANGEROUS AT THE OPERATIONAL LEVEL.
Data retrieved from NASA's ASRS site as of May 2009 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.