 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
TRACON controller and the pilot reported the pilot deviated from the local obstacle departure procedure.
| Attributes | |
| ACN | 1760966 |
| Time | |
| Date | 202009 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | C83.Airport |
| State Reference | CA |
| Environment | |
| Flight Conditions | Marginal |
| Aircraft 1 | |
| Make Model Name | Small Aircraft |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Climb |
| Route In Use | Other ODP |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach Trainee |
| Person 2 | |
| Function | Pilot Flying Single Pilot |
| Experience | Flight Crew Last 90 Days 16 Flight Crew Total 4500 Flight Crew Type 1100 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
The controller working flight data at the time cleared an aircraft off of C83 via the obstacle departure procedure (odp). Flight data then coordinated the departure climbing to 4;000 ft. On the odp with me. I was working the sector responsible for the airport at the time and released the departure. I radar identified the departure aircraft; verified altitude and climbed them to 6;000 ft. As the aircraft was maneuvering in the climb it appeared they were not on the odp. I then asked the pilot to verify they were climbing via the odp. The pilot responded that they were direct to a fix but have the terrain in sight. At this time the aircraft was climbing through 2;600 ft. In a 3;000 ft. MVA (minimum vectoring altitude) on a heading towards higher terrain. At this facility we are able to vector below the MVA as long as the aircraft is not restricted below the MVA and within 900 ft. Of the MVA. Using the '900 ft. Rule' I issued a low altitude alert and a turn away from higher terrain. I also re-cleared them to climb to 6;000 ft. Immediately. After the aircraft was above the mvas I continued vectors to destination and issued a brasher warning with a number to call upon landing.I believe this event was the result of a pilot deviation. I do not think anything could have been done to prevent this event as a controller.
Original NASA ASRS Text
Title: TRACON Controller and the pilot reported the pilot deviated from the local Obstacle Departure Procedure.
Narrative: The controller working Flight Data at the time cleared an aircraft off of C83 via the obstacle departure procedure (ODP). Flight Data then coordinated the departure climbing to 4;000 ft. on the ODP with me. I was working the sector responsible for the airport at the time and released the departure. I radar identified the departure aircraft; verified altitude and climbed them to 6;000 ft. As the aircraft was maneuvering in the climb it appeared they were not on the ODP. I then asked the pilot to verify they were climbing via the ODP. The pilot responded that they were direct to a fix but have the terrain in sight. At this time the aircraft was climbing through 2;600 ft. in a 3;000 ft. MVA (Minimum Vectoring Altitude) on a heading towards higher terrain. At this facility we are able to vector below the MVA as long as the aircraft is not restricted below the MVA and within 900 ft. of the MVA. Using the '900 ft. rule' I issued a low altitude alert and a turn away from higher terrain. I also re-cleared them to climb to 6;000 ft. immediately. After the aircraft was above the MVAs I continued vectors to destination and issued a Brasher warning with a number to call upon landing.I believe this event was the result of a pilot deviation. I do not think anything could have been done to prevent this event as a controller.
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.