 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZOB controller assumes routing without checking the field strip flight plan which results in an operational error.
| Attributes | |
| ACN | 529342 |
| Time | |
| Date | 200111 |
| Day | Thu |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | navaid : air.vor |
| State Reference | OH |
| Altitude | msl bound lower : 28000 msl bound upper : 31000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zob.artcc artcc : zid.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | B757-200 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | other other vortac |
| Flight Phase | cruise : enroute altitude change |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | artcc : zob.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | B727 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | cruise : level |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Experience | flight time total : 1200 |
| ASRS Report | 529342 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : published procedure non adherence : required legal separation |
| Independent Detector | atc equipment : conflict alert other controllera |
| Resolutory Action | controller : issued new clearance |
| Consequence | faa : investigated |
| Miss Distance | horizontal : 18600 vertical : 800 |
| Supplementary | |
| Problem Areas | ATC Human Performance |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
Aircraft #1 was wbound on J80. Aircraft #2 was south of J80, on handoff to my sector. The route was to bwi over mgw VOR. I thought by track and leader line that the #2 aircraft was direct to mgw VOR, but the route had been changed just prior to handoff to air VOR, then mgw VOR. The ZID controller asked for aircraft #1 to descend to FL280. I did and shipped aircraft #1 to ZID. At the time, the leader line on aircraft #2 was behind and still showed a southeast direction (away from aircraft #1). When I saw the aircraft #2 heading for air VOR and aircraft #1 route, I turned aircraft #2 south, but still lost separation. The routing aircraft #$2 was on, was a recent change to 'standard' routing from previous yrs. Suggestion: verify whole route on strip, not just destination.
Original NASA ASRS Text
Title: ZOB CTLR ASSUMES ROUTING WITHOUT CHKING THE FIELD STRIP FLT PLAN WHICH RESULTS IN AN OPERROR.
Narrative: ACFT #1 WAS WBOUND ON J80. ACFT #2 WAS S OF J80, ON HDOF TO MY SECTOR. THE RTE WAS TO BWI OVER MGW VOR. I THOUGHT BY TRACK AND LEADER LINE THAT THE #2 ACFT WAS DIRECT TO MGW VOR, BUT THE RTE HAD BEEN CHANGED JUST PRIOR TO HDOF TO AIR VOR, THEN MGW VOR. THE ZID CTLR ASKED FOR ACFT #1 TO DSND TO FL280. I DID AND SHIPPED ACFT #1 TO ZID. AT THE TIME, THE LEADER LINE ON ACFT #2 WAS BEHIND AND STILL SHOWED A SE DIRECTION (AWAY FROM ACFT #1). WHEN I SAW THE ACFT #2 HEADING FOR AIR VOR AND ACFT #1 RTE, I TURNED ACFT #2 S, BUT STILL LOST SEPARATION. THE ROUTING ACFT #$2 WAS ON, WAS A RECENT CHANGE TO 'STANDARD' ROUTING FROM PREVIOUS YRS. SUGGESTION: VERIFY WHOLE RTE ON STRIP, NOT JUST DEST.
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.