37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 883530 |
Time | |
Date | 201004 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | PRC.Airport |
State Reference | AZ |
Aircraft 1 | |
Make Model Name | Bonanza 35 |
Operating Under FAR Part | Part 91 |
Flight Phase | Descent |
Aircraft 2 | |
Make Model Name | Skyhawk 172/Cutlass 172 |
Flight Phase | Initial Approach |
Route In Use | Visual Approach |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Person 2 | |
Function | Supervisor / CIC |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | Conflict Airborne Conflict Deviation - Altitude Overshoot Deviation - Procedural Clearance |
Narrative:
I was working ground control. The controller in charge (controller in charge) pointed out that aircraft X; who was given a restriction to stay at or above 6;500 MSL to avoid other pattern traffic; had descended below his altitude restriction without authorization. A cessna 172 that was on base made an evasive maneuver to pass behind aircraft X. The developmental; who was training on local 1; had approximately 5 other aircraft in the pattern at the time of the incident. The pilot deviation certainly reduced safety as the smooth pattern was disrupted and the developmental had to re-sequence all of the pattern traffic. Recommendation; this type of pilot deviation is very typical. The pilot had difficulty taxiing out for departure earlier. As an unknown event; the pilot never even realized that he screwed up and the controllers know that FSDO won't do anything if the deviation is reported. We are held to a very high standard and the pilot is not; something needs to be done regarding enforcement actions on pilots that make constant errors. Additionally; training was taking place on a position that should have been de-combined had we had the staffing to perform training and open all of the positions. If the position had been de-combined; the pilot deviation may have been realized earlier with less traffic volume and complexity.
Original NASA ASRS Text
Title: PRC reporters describe a pilot deviation event when the Pilot failed to comply with an altitude assignment to avoid pattern traffic resulting in a evasive action by another pattern aircraft; the reporters claiming FSDO follow-up action on pilots is questionable.
Narrative: I was working Ground Control. The CIC (Controller in Charge) pointed out that Aircraft X; who was given a restriction to stay at or above 6;500 MSL to avoid other pattern traffic; had descended below his altitude restriction without authorization. A Cessna 172 that was on base made an evasive maneuver to pass behind Aircraft X. The Developmental; who was training on Local 1; had approximately 5 other aircraft in the pattern at the time of the incident. The pilot deviation certainly reduced safety as the smooth pattern was disrupted and the developmental had to re-sequence all of the pattern traffic. Recommendation; this type of pilot deviation is very typical. The Pilot had difficulty taxiing out for departure earlier. As an unknown event; the Pilot never even realized that he screwed up and the controllers know that FSDO won't do anything if the deviation is reported. We are held to a very high standard and the Pilot is not; something needs to be done regarding enforcement actions on pilots that make constant errors. Additionally; training was taking place on a position that should have been de-combined had we had the staffing to perform training and open all of the positions. If the position had been de-combined; the pilot deviation may have been realized earlier with less traffic volume and complexity.
Data retrieved from NASA's ASRS site as of April 2012 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.