 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An SF340 PIC reacts to a wrong call sign usage by ZME controller and fails to make his originally cleared altitude crossing restr 45 mi northeast of mem, tn.
| Attributes | |
| ACN | 472275 |
| Time | |
| Date | 200005 |
| Day | Thu |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | navaid : mem.vortac |
| State Reference | TN |
| Altitude | msl bound lower : 8000 msl bound upper : 10000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zme.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | SF 340A |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | other vortac |
| Flight Phase | descent : intermediate altitude |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 150 flight time total : 6700 |
| ASRS Report | 472275 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : multi engine pilot : instrument pilot : commercial |
| Events | |
| Anomaly | altitude deviation : crossing restriction not met altitude deviation : undershoot non adherence : required legal separation non adherence : published procedure non adherence : clearance other anomaly other |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued advisory controller : issued new clearance |
| Consequence | faa : reviewed incident with flight crew |
| Supplementary | |
| Problem Areas | ATC Human Performance |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
Our aircraft was cleared to cross ltown at 8000 ft. A descent was initiated from 12000 ft to make crossing restr. As our aircraft was descending through 9500 ft, ATC said '1234, you were cleared to cross ltown at 10000 ft.' we initiated a climb back to 10000 ft and leveled off. When we were within 7 mi of ltown, ATC again called, now saying 'air carrier 1234 you were cleared to cross ltown at 8000 ft.' we initiated a descent to make the crossing restr. We then heard ATC calling other similar flight number. ATC then informed us of the similar sounding call signs. I believe that this was caused by ATC using multiple frequencys by 1 controller and less than standard radio phraseology by both ATC and flight crew. It is common during periods of intense radio activity to drop company designator from call sign by both ATC and flcs.
Original NASA ASRS Text
Title: AN SF340 PIC REACTS TO A WRONG CALL SIGN USAGE BY ZME CTLR AND FAILS TO MAKE HIS ORIGINALLY CLRED ALT XING RESTR 45 MI NE OF MEM, TN.
Narrative: OUR ACFT WAS CLRED TO CROSS LTOWN AT 8000 FT. A DSCNT WAS INITIATED FROM 12000 FT TO MAKE XING RESTR. AS OUR ACFT WAS DSNDING THROUGH 9500 FT, ATC SAID '1234, YOU WERE CLRED TO CROSS LTOWN AT 10000 FT.' WE INITIATED A CLB BACK TO 10000 FT AND LEVELED OFF. WHEN WE WERE WITHIN 7 MI OF LTOWN, ATC AGAIN CALLED, NOW SAYING 'ACR 1234 YOU WERE CLRED TO CROSS LTOWN AT 8000 FT.' WE INITIATED A DSCNT TO MAKE THE XING RESTR. WE THEN HEARD ATC CALLING OTHER SIMILAR FLT NUMBER. ATC THEN INFORMED US OF THE SIMILAR SOUNDING CALL SIGNS. I BELIEVE THAT THIS WAS CAUSED BY ATC USING MULTIPLE FREQS BY 1 CTLR AND LESS THAN STANDARD RADIO PHRASEOLOGY BY BOTH ATC AND FLC. IT IS COMMON DURING PERIODS OF INTENSE RADIO ACTIVITY TO DROP COMPANY DESIGNATOR FROM CALL SIGN BY BOTH ATC AND FLCS.
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.