 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier went from one ARTCC sector into another sector without coordination. Operational deviation.
| Attributes | |
| ACN | 175699 |
| Time | |
| Date | 199104 |
| Day | Wed |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | atc facility : gsh |
| State Reference | IN |
| Altitude | msl bound lower : 16000 msl bound upper : 16000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zau tower : ict |
| Operator | common carrier : air carrier |
| Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
| Flight Phase | cruise other |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Experience | controller non radar : 9 controller radar : 8 |
| ASRS Report | 175699 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Experience | controller non radar : 8 controller radar : 6 |
| ASRS Report | 175696 |
| Events | |
| Anomaly | non adherence : published procedure other anomaly other |
| Independent Detector | other controllera |
| Resolutory Action | none taken : anomaly accepted |
| Consequence | Other |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Deviation Intra Facility Coordination Failure |
Narrative:
An airspace violation occurred at the plant sector at ZAU. The goshen sector owns the airspace from 9000' to FL230 at the gsh VOR. They relegate 16000' to FL230 to the plant sector as a 'dump zone' for ord inbound traffic. The gsh sector is required to point out or accomplish a handoff 5 mi prior to entering the plant dump zone. On this date, a supervisor working the gsh sector, with myself at plant, air carrier X at 16000' was allowed to enter and penetrate the plant dump zone with no coordination. I was aware of the limited data block on the aircraft and no other aircraft were involved. When the aircraft was approximately 10 mi inside the plant dump zone, I queried the supervisor at gsh as to why the aircraft was allowed to enter my dump zone. He said we would discuss it later. Later that day (approximately 4 hours), the supervisor approached me about the incident and said he did not know how the aircraft was allowed in the dump zone and offered his apology, stating there was no excuse, but that he would not let it happen again.
Original NASA ASRS Text
Title: ACR WENT FROM ONE ARTCC SECTOR INTO ANOTHER SECTOR WITHOUT COORD. OPERATIONAL DEVIATION.
Narrative: AN AIRSPACE VIOLATION OCCURRED AT THE PLANT SECTOR AT ZAU. THE GOSHEN SECTOR OWNS THE AIRSPACE FROM 9000' TO FL230 AT THE GSH VOR. THEY RELEGATE 16000' TO FL230 TO THE PLANT SECTOR AS A 'DUMP ZONE' FOR ORD INBND TFC. THE GSH SECTOR IS REQUIRED TO POINT OUT OR ACCOMPLISH A HDOF 5 MI PRIOR TO ENTERING THE PLANT DUMP ZONE. ON THIS DATE, A SUPVR WORKING THE GSH SECTOR, WITH MYSELF AT PLANT, ACR X AT 16000' WAS ALLOWED TO ENTER AND PENETRATE THE PLANT DUMP ZONE WITH NO COORD. I WAS AWARE OF THE LIMITED DATA BLOCK ON THE ACFT AND NO OTHER ACFT WERE INVOLVED. WHEN THE ACFT WAS APPROX 10 MI INSIDE THE PLANT DUMP ZONE, I QUERIED THE SUPVR AT GSH AS TO WHY THE ACFT WAS ALLOWED TO ENTER MY DUMP ZONE. HE SAID WE WOULD DISCUSS IT LATER. LATER THAT DAY (APPROX 4 HRS), THE SUPVR APCHED ME ABOUT THE INCIDENT AND SAID HE DID NOT KNOW HOW THE ACFT WAS ALLOWED IN THE DUMP ZONE AND OFFERED HIS APOLOGY, STATING THERE WAS NO EXCUSE, BUT THAT HE WOULD NOT LET IT HAPPEN AGAIN.
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.