 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZID controller does not recognize same altitude conflict when xferring an FA50 to another sector during a sector relief briefing.
| Attributes | |
| ACN | 541810 |
| Time | |
| Date | 200203 |
| Day | Fri |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | navaid : hvq.vor |
| State Reference | WV |
| Altitude | msl bound lower : 35000 msl bound upper : 37000 |
| Environment | |
| Flight Conditions | Marginal |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | artcc : zid.artcc tracon : n90.tracon |
| Operator | common carrier : air carrier |
| Make Model Name | EMB ERJ 145 ER&LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | cruise : level |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | artcc : zid.artcc |
| Operator | general aviation : corporate |
| Make Model Name | Falcon 50 |
| Operating Under FAR Part | Part 135 |
| Flight Phase | cruise : enroute altitude change |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Experience | controller radar : 10 |
| ASRS Report | 541810 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : required legal separation non adherence : published procedure |
| Independent Detector | atc equipment : conflict alert |
| Resolutory Action | controller : issued new clearance |
| Consequence | faa : investigated |
| Miss Distance | horizontal : 24000 vertical : 1500 |
| Supplementary | |
| Problem Areas | ATC Human Performance |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Intra Facility Coordination Failure Operational Error |
Narrative:
My 'picture' was that air carrier X was at FL310 (actually at FL350). I had other traffic sits of an abnormal nature due to WX re-routes and holding traffic for cvg arrs. When I cleared air carrier Y on course leaving FL350, I erroneously missed the traffic (air carrier X) at FL350. Conflict alert activated as I was trying to give a relief briefing. I had already made the frequency switch to air carrier Y to the next controller, so I was only still 'talking' to air carrier X. I made an attempt to turn air carrier X out of the conflict, but the turn was too late to ensure separation.
Original NASA ASRS Text
Title: ZID CTLR DOES NOT RECOGNIZE SAME ALT CONFLICT WHEN XFERRING AN FA50 TO ANOTHER SECTOR DURING A SECTOR RELIEF BRIEFING.
Narrative: MY 'PICTURE' WAS THAT ACR X WAS AT FL310 (ACTUALLY AT FL350). I HAD OTHER TFC SITS OF AN ABNORMAL NATURE DUE TO WX RE-ROUTES AND HOLDING TFC FOR CVG ARRS. WHEN I CLRED ACR Y ON COURSE LEAVING FL350, I ERRONEOUSLY MISSED THE TFC (ACR X) AT FL350. CONFLICT ALERT ACTIVATED AS I WAS TRYING TO GIVE A RELIEF BRIEFING. I HAD ALREADY MADE THE FREQ SWITCH TO ACR Y TO THE NEXT CTLR, SO I WAS ONLY STILL 'TALKING' TO ACR X. I MADE AN ATTEMPT TO TURN ACR X OUT OF THE CONFLICT, BUT THE TURN WAS TOO LATE TO ENSURE SEPARATION.
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.