 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
D10 erred when vectoring an arrival to ftw in lieu of the filed destination of afw; the resulting confusion ending with a loss of separation.
| Attributes | |
| ACN | 911030 |
| Time | |
| Date | 201009 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | AFW.Airport |
| State Reference | TX |
| Aircraft 1 | |
| Make Model Name | Falcon 20FJF/20C/20D/20E/20F |
| Flight Phase | Final Approach |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
I had mistakenly vectored FA20 to ftw instead of his destination of afw about 7 miles apart. When I recognized I had vectored him to the wrong airport; I vectored toward afw. A T38 was on an ILS approach to afw. My plan was to put the FA20 on the downwind and let afw tower provide visual and sequence the FA20 behind the T38. I turned the FA20 toward afw and he immediately reported the airport in sight and I cleared him for the visual approach. I then tried to contact afw tower; but the shout line was not working and they would not answer. The only way to contact them was the telephone and I did not have time for that. I then issued a new heading away from the ILS final and altitude to the FA20 and told him it was a vector to follow traffic. Somewhere in all the confusion that I had caused by issuing all the different headings; altitudes; then approach clearance; then another heading altitude; the FA20 descended to 020 and conflicted with the T38 on the ILS final.
Original NASA ASRS Text
Title: D10 erred when vectoring an arrival to FTW in lieu of the filed destination of AFW; the resulting confusion ending with a loss of separation.
Narrative: I had mistakenly vectored FA20 to FTW instead of his destination of AFW about 7 miles apart. When I recognized I had vectored him to the wrong airport; I vectored toward AFW. A T38 was on an ILS approach to AFW. My plan was to put the FA20 on the downwind and let AFW Tower provide visual and sequence the FA20 behind the T38. I turned the FA20 toward AFW and he immediately reported the airport in sight and I cleared him for the visual approach. I then tried to contact AFW Tower; but the shout line was not working and they would not answer. The only way to contact them was the telephone and I did not have time for that. I then issued a new heading away from the ILS final and altitude to the FA20 and told him it was a vector to follow traffic. Somewhere in all the confusion that I had caused by issuing all the different headings; altitudes; then approach clearance; then another heading altitude; the FA20 descended to 020 and conflicted with the T38 on the ILS final.
Data retrieved from NASA's ASRS site as of April 2012 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.