 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZKC controller described operational deviation when departure aircraft made unexpected turn into adjacent airspace; nearly conflicting with another aircraft.
| Attributes | |
| ACN | 808934 |
| Time | |
| Date | 200810 |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : mci.airport |
| State Reference | MO |
| Altitude | msl single value : 16000 |
| Environment | |
| Flight Conditions | IMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zkc.artcc |
| Operator | other |
| Make Model Name | DC-9 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | cruise : level |
| Route In Use | enroute airway : j24.airway |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Experience | controller time certified in position1 : 19 |
| ASRS Report | 808934 |
| Events | |
| Anomaly | airspace violation : entry non adherence : published procedure non adherence : required legal separation |
| Independent Detector | atc equipment : conflict alert other controllera |
| Resolutory Action | controller : issued alert controller : issued new clearance |
| Consequence | faa : investigated |
| Miss Distance | horizontal : 42000 vertical : 1000 |
| Supplementary | |
| Problem Areas | ATC Human Performance |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Deviation |
Narrative:
DC9 was filed J24 wbound to drivl intersection then direct foe. The LOA with mci approach calls for aircraft to stay over mci; then foe. The aircraft took a left turn at drivl and became a potential confliction with a departure J24 that goes over mci; so I assumed the aircraft would go over mci; but didn't. I noticed him turning at drivl. If hert routing had been on uret; the routing would have been easier to see and the aircraft would have been less likely to make the turn at drivl; because of the visual cue of the blue routing. The controller before me also said they assumed the DC9 was going over mci when they looked at the uret route and saw J24 and foe. If hert routing were applied; both of us would likely have noticed the aircraft was on routing that did not comply with the LOA; and the unexpected turn.
Original NASA ASRS Text
Title: ZKC CONTROLLER DESCRIBED OPERATIONAL DEVIATION WHEN DEPARTURE AIRCRAFT MADE UNEXPECTED TURN INTO ADJACENT AIRSPACE; NEARLY CONFLICTING WITH ANOTHER AIRCRAFT.
Narrative: DC9 WAS FILED J24 WBOUND TO DRIVL INTXN THEN DIRECT FOE. THE LOA WITH MCI APCH CALLS FOR ACFT TO STAY OVER MCI; THEN FOE. THE ACFT TOOK A L TURN AT DRIVL AND BECAME A POTENTIAL CONFLICTION WITH A DEP J24 THAT GOES OVER MCI; SO I ASSUMED THE ACFT WOULD GO OVER MCI; BUT DIDN'T. I NOTICED HIM TURNING AT DRIVL. IF HERT ROUTING HAD BEEN ON URET; THE ROUTING WOULD HAVE BEEN EASIER TO SEE AND THE ACFT WOULD HAVE BEEN LESS LIKELY TO MAKE THE TURN AT DRIVL; BECAUSE OF THE VISUAL CUE OF THE BLUE ROUTING. THE CTLR BEFORE ME ALSO SAID THEY ASSUMED THE DC9 WAS GOING OVER MCI WHEN THEY LOOKED AT THE URET RTE AND SAW J24 AND FOE. IF HERT ROUTING WERE APPLIED; BOTH OF US WOULD LIKELY HAVE NOTICED THE ACFT WAS ON ROUTING THAT DID NOT COMPLY WITH THE LOA; AND THE UNEXPECTED TURN.
Data retrieved from NASA's ASRS site as of May 2009 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.