37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1148243 |
Time | |
Date | 201402 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | PGD.Airport |
State Reference | FL |
Aircraft 1 | |
Make Model Name | PA-46 Malibu Meridian |
Flight Phase | Final Approach |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural FAR Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT |
Narrative:
I was working final radar when the PA46 checked in on course to pgd. The pilot requested the RNAV runway 33 approach at pgd. I coordinated with the tower and they approved the approach. I gave the aircraft a 160 heading in order to comply with his request. The pilot followed my instructions and flew the 160 heading. The pilot then asked for lower; and I descended him to 2;500 from his original 3;000. A couple miles later he asked me for lower again. I advised that I was unable to descend him any lower because of the antennas [in the vicinity] and that was the [initial] altitude of the approach he was requesting. When the pilot got abeam the final approach fix; I cleared him to '...turn right direct petse; four miles from petse; cross petse at 2;500; cleared RNAV runway 33 approach'. The pilot read back; 'turn direct petse; cleared approach'. I didn't see anything wrong with that because the altitude is published on the approach plate. After a couple of sweeps on the radar scope; the pilot descended from 2;500 to 1;500 MSL less than half a mile from the antennas at serfs. When I noticed it; I told the pilot that he was supposed to cross petse at 2;500 and that was why I could not descend him any lower. His response was; 'oh'. I notified my cicr regarding this issue and he called pgd tower to notify the pilot to call our facility; which he didn't do.
Original NASA ASRS Text
Title: Despite repeated attempts by the TRACON Controller to make him aware; the pilot of a PA46 failed to comply with the altitude constraints associated with the RNAV (GPS) Runway 33 approach to PGD. The pilot also failed to contact the facility to review the incident as requested.
Narrative: I was working Final radar when the PA46 checked in on course to PGD. The pilot requested the RNAV Runway 33 Approach at PGD. I coordinated with the Tower and they approved the approach. I gave the aircraft a 160 heading in order to comply with his request. The pilot followed my instructions and flew the 160 heading. The pilot then asked for lower; and I descended him to 2;500 from his original 3;000. A couple miles later he asked me for lower again. I advised that I was unable to descend him any lower because of the antennas [in the vicinity] and that was the [initial] altitude of the approach he was requesting. When the pilot got abeam the final approach fix; I cleared him to '...turn right direct PETSE; four miles from PETSE; cross PETSE at 2;500; cleared RNAV Runway 33 Approach'. The pilot read back; 'Turn direct PETSE; cleared approach'. I didn't see anything wrong with that because the altitude is published on the approach plate. After a couple of sweeps on the radar scope; the pilot descended from 2;500 to 1;500 MSL less than half a mile from the antennas at SERFS. When I noticed it; I told the pilot that he was supposed to cross PETSE at 2;500 and that was why I could not descend him any lower. His response was; 'OH'. I notified my CICR regarding this issue and he called PGD Tower to notify the pilot to call our facility; which he didn't do.
Data retrieved from NASA's ASRS site 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.