 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Phl TRACON controller observed B737 descend below assigned altitude and makes reference to previous 'phantom controller.'
| Attributes | |
| ACN | 672038 |
| Time | |
| Date | 200509 |
| Place | |
| Locale Reference | airport : phl.airport |
| State Reference | PA |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : phl.tracon |
| Operator | common carrier : air carrier |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | descent : approach |
| Route In Use | arrival : on vectors |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : approach |
| Qualification | controller : radar |
| Experience | controller non radar : 3 controller radar : 12 |
| ASRS Report | 672038 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Events | |
| Anomaly | altitude deviation : excursion from assigned altitude |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued alert controller : issued new clearance |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
B737 was on a normal vector for the left downwind to runway 27R at phl. I had assigned 6000 ft. I first noticed that his altitude indicated 5200 ft and asked the pilot to verify assigned altitude. The pilot responded 'you gave us 2000 ft.' I advised him that I had not assigned any aircraft 2000 ft and asked him to verify that he was not monitoring another frequency. He then stated; 'no; twenty-six six is all we've got up' and then said 'we read it back.' the area he descended in can be a heavily trafficked area; but luckily at this time there was no traffic conflict. I then coordination and assigned him 4000 ft. After I was relieved from position; I asked the supervisor to review the tape. I reviewed that tape and confirmed that I had never assigned him 2000 ft as he stated. It is possible that this could have been a 'phantom controller' which has occurred in the phl area in the past.
Original NASA ASRS Text
Title: PHL TRACON CTLR OBSERVED B737 DSND BELOW ASSIGNED ALT AND MAKES REF TO PREVIOUS 'PHANTOM CTLR.'
Narrative: B737 WAS ON A NORMAL VECTOR FOR THE L DOWNWIND TO RWY 27R AT PHL. I HAD ASSIGNED 6000 FT. I FIRST NOTICED THAT HIS ALT INDICATED 5200 FT AND ASKED THE PLT TO VERIFY ASSIGNED ALT. THE PLT RESPONDED 'YOU GAVE US 2000 FT.' I ADVISED HIM THAT I HAD NOT ASSIGNED ANY ACFT 2000 FT AND ASKED HIM TO VERIFY THAT HE WAS NOT MONITORING ANOTHER FREQ. HE THEN STATED; 'NO; TWENTY-SIX SIX IS ALL WE'VE GOT UP' AND THEN SAID 'WE READ IT BACK.' THE AREA HE DSNDED IN CAN BE A HEAVILY TRAFFICKED AREA; BUT LUCKILY AT THIS TIME THERE WAS NO TFC CONFLICT. I THEN COORD AND ASSIGNED HIM 4000 FT. AFTER I WAS RELIEVED FROM POS; I ASKED THE SUPVR TO REVIEW THE TAPE. I REVIEWED THAT TAPE AND CONFIRMED THAT I HAD NEVER ASSIGNED HIM 2000 FT AS HE STATED. IT IS POSSIBLE THAT THIS COULD HAVE BEEN A 'PHANTOM CTLR' WHICH HAS OCCURRED IN THE PHL AREA IN THE PAST.
Data retrieved from NASA's ASRS site as of January 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.