 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZID controller experienced operational error at FL240 when trying to separate opposite direction traffic from adjacent center.
| Attributes | |
| ACN | 747949 |
| Time | |
| Date | 200707 |
| Place | |
| Locale Reference | atc facility : zid.artcc |
| State Reference | IN |
| Altitude | msl single value : 24000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zid.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | A320 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | descent : approach |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | artcc : zid.artcc |
| Operator | general aviation : corporate |
| Make Model Name | Beechjet 400 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | cruise : level |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Experience | controller limited radar : 4 controller radar : 3 controller time certified in position1 : 3 flight time total : 200 |
| ASRS Report | 747949 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : required legal separation |
| Independent Detector | atc equipment : conflict alert other controllera |
| Resolutory Action | controller : issued new clearance controller : issued alert flight crew : took evasive action |
| Consequence | faa : investigated |
| Miss Distance | horizontal : 1800 vertical : 700 |
| Supplementary | |
| Problem Areas | ATC Human Performance |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
I issued aircraft X a ZME/ZID boundary crossing at FL200. I observed a limited data block approximately 15 NM south of the boundary head on with aircraft X at FL240. I called M63 to find out who the ldb was. It was an evv arrival. I decided to stop aircraft X (bna arrival) and descend him respect the evv arrival. I amended aircraft X to maintain FL240 because I believed he was descending too fast for an uneventful level at FL250. And due to LOA and what a ZME controller said I was under the impression that the evv arrival would be descending. As it became apparent no action was being taken with aircraft Y (evv arrival); I initiated vectors with aircraft X and a descent clearance.
Original NASA ASRS Text
Title: ZID CTLR EXPERIENCED OPERROR AT FL240 WHEN TRYING TO SEPARATE OPPOSITE DIRECTION TFC FROM ADJACENT CENTER.
Narrative: I ISSUED ACFT X A ZME/ZID BOUNDARY XING AT FL200. I OBSERVED A LIMITED DATA BLOCK APPROX 15 NM S OF THE BOUNDARY HEAD ON WITH ACFT X AT FL240. I CALLED M63 TO FIND OUT WHO THE LDB WAS. IT WAS AN EVV ARR. I DECIDED TO STOP ACFT X (BNA ARR) AND DSND HIM RESPECT THE EVV ARR. I AMENDED ACFT X TO MAINTAIN FL240 BECAUSE I BELIEVED HE WAS DSNDING TOO FAST FOR AN UNEVENTFUL LEVEL AT FL250. AND DUE TO LOA AND WHAT A ZME CTLR SAID I WAS UNDER THE IMPRESSION THAT THE EVV ARR WOULD BE DSNDING. AS IT BECAME APPARENT NO ACTION WAS BEING TAKEN WITH ACFT Y (EVV ARR); I INITIATED VECTORS WITH ACFT X AND A DSCNT CLRNC.
Data retrieved from NASA's ASRS site as of January 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.