37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 617055 |
Time | |
Date | 200405 |
Day | Mon |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : teb.airport |
State Reference | NJ |
Altitude | msl bound lower : 2000 msl bound upper : 2500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : n90.tracon |
Operator | general aviation : personal |
Make Model Name | PC-12 |
Operating Under FAR Part | Part 91 |
Flight Phase | descent : approach |
Route In Use | approach : visual |
Flight Plan | IFR |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : multi engine pilot : instrument pilot : commercial |
Experience | flight time total : 1750 flight time type : 20 |
ASRS Report | 617055 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Events | |
Anomaly | altitude deviation : crossing restriction not met non adherence : published procedure non adherence : clearance |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance controller : issued advisory |
Supplementary | |
Problem Areas | ATC Human Performance Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Pilot was cleared for the VOR/dma a approach into teb with an overhead entry into the left downwind for runway 24. Pilot was instructed to pass over wanes at 3000 ft and clifo at 2000 ft. The aircraft passed over clifo at 2500 ft MSL instead of 2000 ft as instructed. Controller advised me of the deviation. During the approach the controller never verbally cleared me for the approach. So I became confused as to whether I was on the visual once I had the airport in sight. The confusion was further exacerbated by the announcement of the crossing altitude rests. After all, if I had been cleared for the approach, why would the controller verbally announce the restrs, they were published right on the plate! Further, the controller didn't mention any restrs related to jaymo. I got the feeling that the controller wanted me to go visual, disregard the jaymo altitude restr, but adhere to the approach procedure in terms of clifo intersection. While contemplating the merits of remaining at 2500 ft for jaymo, I neglected to descend for the clifo restr.
Original NASA ASRS Text
Title: PC12 PLT MISSED MANDATORY CROSSING ALT DURING APCH TO TEB.
Narrative: PLT WAS CLRED FOR THE VOR/DMA A APCH INTO TEB WITH AN OVERHEAD ENTRY INTO THE LEFT DOWNWIND FOR RWY 24. PLT WAS INSTRUCTED TO PASS OVER WANES AT 3000 FT AND CLIFO AT 2000 FT. THE ACFT PASSED OVER CLIFO AT 2500 FT MSL INSTEAD OF 2000 FT AS INSTRUCTED. CTLR ADVISED ME OF THE DEVIATION. DURING THE APCH THE CTLR NEVER VERBALLY CLRED ME FOR THE APCH. SO I BECAME CONFUSED AS TO WHETHER I WAS ON THE VISUAL ONCE I HAD THE ARPT IN SIGHT. THE CONFUSION WAS FURTHER EXACERBATED BY THE ANNOUNCEMENT OF THE CROSSING ALT RESTS. AFTER ALL, IF I HAD BEEN CLRED FOR THE APCH, WHY WOULD THE CTLR VERBALLY ANNOUNCE THE RESTRS, THEY WERE PUBLISHED RIGHT ON THE PLATE! FURTHER, THE CTLR DIDN'T MENTION ANY RESTRS RELATED TO JAYMO. I GOT THE FEELING THAT THE CTLR WANTED ME TO GO VISUAL, DISREGARD THE JAYMO ALT RESTR, BUT ADHERE TO THE APCH PROC IN TERMS OF CLIFO INTERSECTION. WHILE CONTEMPLATING THE MERITS OF REMAINING AT 2500 FT FOR JAYMO, I NEGLECTED TO DESCEND FOR THE CLIFO RESTR.
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.