37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1512452 |
Time | |
Date | 201801 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | F11.TRACON |
State Reference | FL |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft Low Wing 1 Eng Retractable Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Route In Use | Vectors |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | Visual Approach |
Flight Plan | IFR |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | Deviation - Procedural FAR Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
Aircraft X called me 4 miles south of the final requesting a VFR class C airspace transition to an airport. I radar identified the aircraft; and told the pilot to fly westbound to avoid traffic on the sfb final. He failed to comply. I issued traffic to aircraft X; and another turn with a heading of 270 to avoid. He did not see the traffic; and still failed to turn. I instructed a 3rd time to please turn to avoid. I then issued traffic for an aircraft on final that he was in close proximity to aircraft Y; who was already on a visual approach clearance to a nearby airport. Aircraft X reported the traffic in sight eventually; and said he would maintain visual separation. I still issued a turn of 270 to avoid an RA/TCAS situation; and explained it to aircraft X the reason why I was still turning the aircraft due to the targets so close to each other. He never turned to a 270 heading; so I had to stop aircraft Y from descending. They crossed out over each other with aircraft Y at 1600 and aircraft X at 1100. Once the conflict was resolved I allowed aircraft Y to continue the visual approach; and apologized to him for the aircraft X getting in the way. Aircraft Y landed without incident. I then asked aircraft X why he bothered to request flight following if he was not going to obey instructions. His response was that since he was outside the class bravo airspace he did not need to obey anything I said; and just wanted to transition the class charlie airspace. I then reiterated the fact that he was going to cause a TCAS/RA situation with someone; even if he had the traffic in sight in the future. I also stated that if he had not called me for flight following; I would have worked around the aircraft I was not in communication with; but since he had called me; I was expecting him to follow instructions. He proceeded to turn his transponder to code 1200. The pilot may be correct in the fact that he was not in the class B airspace; but he was knowingly creating an unsafe situation. Upon further research/questioning; another controller had an incident similar to the one I just had today on a previous occasion with the same aircraft.
Original NASA ASRS Text
Title: MCO Tracon Controller reported a pilot receiving VFR flight following refused to comply with ATC issued vectors for traffic.
Narrative: Aircraft X called me 4 miles south of the final requesting a VFR Class C airspace transition to an airport. I radar identified the aircraft; and told the pilot to fly westbound to avoid traffic on the SFB final. He failed to comply. I issued traffic to Aircraft X; and another turn with a heading of 270 to avoid. He did not see the traffic; and still failed to turn. I instructed a 3rd time to please turn to avoid. I then issued traffic for an aircraft on final that he was in close proximity to Aircraft Y; who was already on a visual approach clearance to a nearby airport. Aircraft X reported the traffic in sight eventually; and said he would maintain visual separation. I still issued a turn of 270 to avoid an RA/TCAS situation; and explained it to Aircraft X the reason why I was still turning the aircraft due to the targets so close to each other. He never turned to a 270 heading; so I had to stop Aircraft Y from descending. They crossed out over each other with Aircraft Y at 1600 and Aircraft X at 1100. Once the conflict was resolved I allowed Aircraft Y to continue the visual approach; and apologized to him for the Aircraft X getting in the way. Aircraft Y landed without incident. I then asked Aircraft X why he bothered to request flight following if he was not going to obey instructions. His response was that since he was outside the Class Bravo airspace he did not need to obey anything I said; and just wanted to transition the Class Charlie airspace. I then reiterated the fact that he was going to cause a TCAS/RA situation with someone; even if he had the traffic in sight in the future. I also stated that if he had not called me for flight following; I would have worked around the aircraft I was not in communication with; but since he had called me; I was expecting him to follow instructions. He proceeded to turn his transponder to code 1200. The pilot may be correct in the fact that he was not in the Class B airspace; but he was knowingly creating an unsafe situation. Upon further research/questioning; another controller had an incident similar to the one I just had today on a previous occasion with the same aircraft.
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.