 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
TRACON controller reported a clearance problem which led to an aircraft being below the minimum vectoring altitude.
| Attributes | |
| ACN | 1599358 |
| Time | |
| Date | 201811 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZZZ.TRACON |
| State Reference | US |
| Aircraft 1 | |
| Make Model Name | PA-28 Cherokee/Archer/Dakota/Pillan/Warrior |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Initial Climb |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 4 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Clearance Inflight Event / Encounter CFTT / CFIT |
Narrative:
Clearance delivery gave aircraft X his clearance. He was issued the odp [obstacle departure procedure] climbing to 5;000 [feet]. Clearance delivery coordinated with me the release at which time I gave a release. Upon departure; aircraft X checked on with me and stated his altitude leaving and stated that he was climbing to 3;100 [feet]. I did not pay much attention to this because he was assigned 5;000 [feet] and clearance delivery reassured me of his correct read back. See as the odp [obstacle departure procedure] initial altitude was climb runway heading to 3;100 [feet] then climbing left turn direct to VOR. When the aircraft reported climbing to 3;100 [feet]; I assumed that only meant initially and then would continue his climb per his clearance and the odp. The aircraft didn't seem to be climbing very fast; so I re-inquired with him the altitude he was climbing to. After stating again 3;100 [feet]; I reissued 5;000 [feet]. Because he was not making a turn; I then complied by the 900 feet rule and climbed him once leaving 3;300 [feet] in a 4;200 [feet] MVA. Qa/qc deemed that because he told me that he was only climbing to 3;100 [feet] even though his clearance was to 5;000 [feet] and I did not immediately correct this; that I had a significant MVA event. I would recommend not punishing a controller for a pilot deviation.
Original NASA ASRS Text
Title: TRACON Controller reported a clearance problem which led to an aircraft being below the Minimum Vectoring Altitude.
Narrative: Clearance delivery gave Aircraft X his clearance. He was issued the ODP [Obstacle Departure Procedure] climbing to 5;000 [feet]. Clearance Delivery coordinated with me the release at which time I gave a release. Upon departure; Aircraft X checked on with me and stated his altitude leaving and stated that he was climbing to 3;100 [feet]. I did not pay much attention to this because he was assigned 5;000 [feet] and Clearance Delivery reassured me of his correct read back. See as the ODP [Obstacle Departure Procedure] initial altitude was climb runway heading to 3;100 [feet] then climbing left turn direct to VOR. When the aircraft reported climbing to 3;100 [feet]; I assumed that only meant initially and then would continue his climb per his clearance and the ODP. The aircraft didn't seem to be climbing very fast; so I re-inquired with him the altitude he was climbing to. After stating again 3;100 [feet]; I reissued 5;000 [feet]. Because he was not making a turn; I then complied by the 900 feet rule and climbed him once leaving 3;300 [feet] in a 4;200 [feet] MVA. QA/QC deemed that because he told me that he was only climbing to 3;100 [feet] even though his clearance was to 5;000 [feet] and I did not immediately correct this; that I had a significant MVA event. I would recommend not punishing a controller for a pilot deviation.
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.