37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1093522 |
Time | |
Date | 201306 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Aircraft 1 | |
Make Model Name | B757 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
I was vectoring the final to runway 12 at TRACON; (west approach). A BE30 was working in south approach; immediately south and adjacent to my airspace. A point out was given to me by the south approach controller. This coordination included the BE30 aircraft was to slightly penetrate my airspace by going to a 12 mile final. I observed the BE30 aircraft on the final to the adjacent airport so I turned my traffic inbound to [the class C airport]. Then I observed the BE30 aircraft reverse course; toward my traffic. Apparently the BE30 aircraft needed to intercept his final from the north side. I was not aware; or at least didn't fully understand the requested route by the BE30 aircraft. Both my aircraft and the flight check aircraft were at 3;000 MSL. I immediately vectored my B757 away from flight check and initiated a climb. I was turning to a 160 heading to join the localizer and turned my aircraft away; to the right heading 220. I believed this heading would provide the necessary course divergence separation. Better coordination; in detail; of flight check requirements. I have for years wondered why flight check cannot provide a detailed request of their requirements to the facility; prior to their arrival. This would allow for proper planning and quite possibly better service to the flight check organization. Making this up as you go along can lead to confusion; (as I believe was the case here); and possibly create a less safe environment for all.
Original NASA ASRS Text
Title: TRACON Controller described a conflict event during Flight Check operations noting that increased and detailed coordination between Flight Check and local ATC facilities is needed.
Narrative: I was vectoring the final to Runway 12 at TRACON; (West Approach). A BE30 was working in South Approach; immediately South and adjacent to my airspace. A point out was given to me by the South Approach Controller. This coordination included the BE30 aircraft was to slightly penetrate my airspace by going to a 12 mile final. I observed the BE30 aircraft on the final to the adjacent airport so I turned my traffic inbound to [the Class C airport]. Then I observed the BE30 aircraft reverse course; toward my traffic. Apparently the BE30 aircraft needed to intercept his final from the north side. I was not aware; or at least didn't fully understand the requested route by the BE30 aircraft. Both my aircraft and the flight check aircraft were at 3;000 MSL. I immediately vectored my B757 away from flight check and initiated a climb. I was turning to a 160 heading to join the localizer and turned my aircraft away; to the right heading 220. I believed this heading would provide the necessary course divergence separation. Better coordination; in detail; of Flight Check requirements. I have for years wondered why flight check cannot provide a detailed request of their requirements to the facility; prior to their arrival. This would allow for proper planning and quite possibly better service to the flight check organization. Making this up as you go along can lead to confusion; (as I believe was the case here); and possibly create a less safe environment for all.
Data retrieved from NASA's ASRS site as of July 2013 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.