37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 391873 |
Time | |
Date | 199801 |
Day | Sat |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : phx |
State Reference | AZ |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : phx |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | other : unknown |
Aircraft 2 | |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | other : unknown |
Person 1 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | controller : radar |
Experience | controller non radar : 5 controller radar : 10 |
ASRS Report | 391873 |
Person 2 | |
Affiliation | Other |
Function | flight crew : single pilot |
Events | |
Anomaly | non adherence : published procedure non adherence : far other anomaly other other anomaly other |
Independent Detector | other controllera |
Resolutory Action | none taken : unable |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Situations | |
ATC Facility | procedure or policy : unspecified |
Narrative:
While working control position at phx TRACON, I tracked several class B violations. I observed 3 separate aircraft transition class B airspace without communications with ATC at XA00, XA38, and XB23. These are not isolated incidents and I believe such violations occur in excess of 10 times daily. My concern is that due to workload constraints these incidents go unrpted. The vast majority go unidented. The few that are idented are normally given a verbal warning by the controller or supervisor on duty. Pilot deviation reports are filed on less than 1% of the total violations. Although the resources may not exist for filing incident reports as required by the 7210.3M directive, by not keeping any record of the volume of these violations we are failing to provide an accurate account of the integrity of class B airspace. I believe there should be some record kept indicating that several thousand aircraft violate the phx class B airspace yrly. This information might be useful in pilot education.
Original NASA ASRS Text
Title: RPTR CLAIMS THERE WERE 3 CLASS B VIOLATIONS WITHOUT COM TO APCH. RPTR BELIEVES THERE ARE IN EXCESS OF 10 OF THESE PER DAY.
Narrative: WHILE WORKING CTL POS AT PHX TRACON, I TRACKED SEVERAL CLASS B VIOLATIONS. I OBSERVED 3 SEPARATE ACFT TRANSITION CLASS B AIRSPACE WITHOUT COMS WITH ATC AT XA00, XA38, AND XB23. THESE ARE NOT ISOLATED INCIDENTS AND I BELIEVE SUCH VIOLATIONS OCCUR IN EXCESS OF 10 TIMES DAILY. MY CONCERN IS THAT DUE TO WORKLOAD CONSTRAINTS THESE INCIDENTS GO UNRPTED. THE VAST MAJORITY GO UNIDENTED. THE FEW THAT ARE IDENTED ARE NORMALLY GIVEN A VERBAL WARNING BY THE CTLR OR SUPVR ON DUTY. PLTDEV RPTS ARE FILED ON LESS THAN 1% OF THE TOTAL VIOLATIONS. ALTHOUGH THE RESOURCES MAY NOT EXIST FOR FILING INCIDENT RPTS AS REQUIRED BY THE 7210.3M DIRECTIVE, BY NOT KEEPING ANY RECORD OF THE VOLUME OF THESE VIOLATIONS WE ARE FAILING TO PROVIDE AN ACCURATE ACCOUNT OF THE INTEGRITY OF CLASS B AIRSPACE. I BELIEVE THERE SHOULD BE SOME RECORD KEPT INDICATING THAT SEVERAL THOUSAND ACFT VIOLATE THE PHX CLASS B AIRSPACE YRLY. THIS INFO MIGHT BE USEFUL IN PLT EDUCATION.
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.