37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1269517 |
Time | |
Date | 201506 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | GSP.TRACON |
State Reference | SC |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft |
Flight Phase | Final Approach |
Route In Use | Other Instrument Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Small Aircraft Low Wing 1 Eng Retractable Gear |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 6.75 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
The previous controller approved an opposite direction IFR approach to a satellite airport just prior to me getting briefed for the position. Gmu ATCT was advertising runway 19. Aircraft X requested and was approved for an opposite direction ILS runway 1 approach and coordination was effected and complete. I took over the position; vectoring and clearing aircraft X for the ILS approach. Meanwhile arriving from the north IFR to gmu requesting a visual approach to runway 19 was aircraft Y. I assigned aircraft Y a westbound heading and to maintain 3;000. I then switched aircraft X to gmu ATCT. Shortly after aircraft X dropped off the radar on short final; I verified aircraft Y had the airport in sight and cleared him for the visual approach to runway 19. It was later brought to my attention that aircraft Y needed to be at least 10 miles from the airport prior to being cleared visual approach and aircraft X on the ground. Safety and separation was not an issue as aircraft Y was at least 5 miles from the airport when aircraft X touched down.in this day and age; opposite direction approaches provide no significant benefit to the operation under normal circumstances especially with all of the required coordination and separation. Therefore; I will not be authorizing opposite direction approaches anymore.
Original NASA ASRS Text
Title: A GSP TRACON Controller reports of a deviation to the Opposite Direction Operation because the second aircraft was not within the standards for the operation to occur.
Narrative: The previous controller approved an opposite direction IFR approach to a satellite airport just prior to me getting briefed for the position. GMU ATCT was advertising Runway 19. Aircraft X requested and was approved for an opposite direction ILS Runway 1 approach and coordination was effected and complete. I took over the position; vectoring and clearing Aircraft X for the ILS approach. Meanwhile arriving from the north IFR to GMU requesting a visual approach to Runway 19 was Aircraft Y. I assigned Aircraft Y a westbound heading and to maintain 3;000. I then switched Aircraft X to GMU ATCT. Shortly after Aircraft X dropped off the radar on short final; I verified Aircraft Y had the airport in sight and cleared him for the visual approach to Runway 19. It was later brought to my attention that Aircraft Y needed to be at least 10 miles from the airport prior to being cleared visual approach and Aircraft X on the ground. Safety and separation was not an issue as Aircraft Y was at least 5 miles from the airport when Aircraft X touched down.In this day and age; opposite direction approaches provide no significant benefit to the operation under normal circumstances especially with all of the required coordination and separation. Therefore; I will not be authorizing opposite direction approaches anymore.
Data retrieved from NASA's ASRS site 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.