 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZID controller experienced operational error at FL300 when distracted by checking re-routes and failing to note slow descent of one aircraft.
| Attributes | |
| ACN | 792522 |
| Time | |
| Date | 200806 |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | navaid : ape.vortac |
| State Reference | OH |
| Altitude | msl single value : 30000 |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zid.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | Regional Jet 200 ER&LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | cruise : level |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | artcc : zid.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | Regional Jet 200 ER&LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | descent : vacating altitude |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Experience | controller radar : 17 |
| ASRS Report | 792522 |
| 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 |
| Consequence | faa : investigated |
| Miss Distance | horizontal : 10020 vertical : 800 |
| Supplementary | |
| Problem Areas | ATC Human Performance Weather |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
Aircraft #1 was nwbound at FL300. Aircraft #2 nebound at FL310 with a crossing at FL240. There was a third aircraft that was flying wbound at FL340. I had a note that the third aircraft needed to be routed differently for WX. I saw that the rerte was going to put the third aircraft into more WX. I asked my supervisor about rerte; he thought it was canceled and went to check with traffic management. Since I wasn't getting an answer; I had to look on the maps for a route that would get the third aircraft to its destination without encountering WX. I became fixated on this problem and did not notice the second aircraft had not started to descend. This was the third day of my work week involving WX. The previous days were filled with rertes that didn't work and I was getting upset that no one had a clue as to what was going on. I let myself be distraction.
Original NASA ASRS Text
Title: ZID CTLR EXPERIENCED OPERROR AT FL300 WHEN DISTRACTED BY CHECKING RE-ROUTES AND FAILING TO NOTE SLOW DESCENT OF ONE ACFT.
Narrative: ACFT #1 WAS NWBOUND AT FL300. ACFT #2 NEBOUND AT FL310 WITH A XING AT FL240. THERE WAS A THIRD ACFT THAT WAS FLYING WBOUND AT FL340. I HAD A NOTE THAT THE THIRD ACFT NEEDED TO BE ROUTED DIFFERENTLY FOR WX. I SAW THAT THE RERTE WAS GOING TO PUT THE THIRD ACFT INTO MORE WX. I ASKED MY SUPVR ABOUT RERTE; HE THOUGHT IT WAS CANCELED AND WENT TO CHK WITH TFC MGMNT. SINCE I WASN'T GETTING AN ANSWER; I HAD TO LOOK ON THE MAPS FOR A RTE THAT WOULD GET THE THIRD ACFT TO ITS DEST WITHOUT ENCOUNTERING WX. I BECAME FIXATED ON THIS PROB AND DID NOT NOTICE THE SECOND ACFT HAD NOT STARTED TO DSND. THIS WAS THE THIRD DAY OF MY WORK WK INVOLVING WX. THE PREVIOUS DAYS WERE FILLED WITH RERTES THAT DIDN'T WORK AND I WAS GETTING UPSET THAT NO ONE HAD A CLUE AS TO WHAT WAS GOING ON. I LET MYSELF BE DISTR.
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.