 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A B737-300 inbound to sdf was cleared to brdon intersection. Crew confused this with brbon intersection which was also in the sdf area; leading to a track deviation.
| Attributes | |
| ACN | 713185 |
| Time | |
| Date | 200610 |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | intersection : brdon |
| State Reference | KY |
| Altitude | msl single value : 20000 |
| Environment | |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | artcc : zid.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | B737-700 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | cruise : level |
| Route In Use | enroute : direct |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Experience | flight time last 90 days : 202 |
| ASRS Report | 713185 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Events | |
| Anomaly | non adherence : clearance other anomaly other other spatial deviation |
| Independent Detector | other controllera other flight crewa |
| Resolutory Action | none taken : detected after the fact |
| Consequence | faa : reviewed incident with flight crew |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance ATC Human Performance Chart Or Publication |
| Primary Problem | Ambiguous |
| Situations | |
| Chart | sectional : rwy 21l |
Narrative:
Enroute to sdf we were cleared direct to brdon intersection direct sdf. I entered bordn into the FMC and saw on the map display that it was not along our route of flight. I asked ATC to repeat the fix and he spelled out brdon which I entered into the FMC. This fix was between us and the airport but it seemed too far east since we were approaching from the northwest and landing north. The captain stated that the correct fix was brbon which is on the localizer to runway 35L. We went direct and few minutes later ATC asked how far we show ourselves from brdon. We passed 7 miles west of brdon. He pointed out our mistake; brbon instead of brdon and handed us off to the next controller. I should have asked ATC to repeat the fix a third time since clearly I did not copy the correct name. Also; I think ATC might want to rename either brdon or brbon since they are so similar and used for the same airport.
Original NASA ASRS Text
Title: A B737-300 INBOUND TO SDF WAS CLRED TO BRDON INTXN. CREW CONFUSED THIS WITH BRBON INTXN WHICH WAS ALSO IN THE SDF AREA; LEADING TO A TRACK DEV.
Narrative: ENROUTE TO SDF WE WERE CLEARED DIRECT TO BRDON INTXN DIRECT SDF. I ENTERED BORDN INTO THE FMC AND SAW ON THE MAP DISPLAY THAT IT WAS NOT ALONG OUR ROUTE OF FLIGHT. I ASKED ATC TO REPEAT THE FIX AND HE SPELLED OUT BRDON WHICH I ENTERED INTO THE FMC. THIS FIX WAS BETWEEN US AND THE ARPT BUT IT SEEMED TOO FAR EAST SINCE WE WERE APPROACHING FROM THE NORTHWEST AND LNDG NORTH. THE CAPT STATED THAT THE CORRECT FIX WAS BRBON WHICH IS ON THE LOC TO RWY 35L. WE WENT DIRECT AND FEW MINUTES LATER ATC ASKED HOW FAR WE SHOW OURSELVES FROM BRDON. WE PASSED 7 MILES WEST OF BRDON. HE POINTED OUT OUR MISTAKE; BRBON INSTEAD OF BRDON AND HANDED US OFF TO THE NEXT CTLR. I SHOULD HAVE ASKED ATC TO REPEAT THE FIX A THIRD TIME SINCE CLEARLY I DID NOT COPY THE CORRECT NAME. ALSO; I THINK ATC MIGHT WANT TO RENAME EITHER BRDON OR BRBON SINCE THEY ARE SO SIMILAR AND USED FOR THE SAME ARPT.
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.