37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1198239 |
Time | |
Date | 201408 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZJX.ARTCC |
State Reference | FL |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft Low Wing 2 Eng Retractable Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 5 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
I was about to switch aircraft X to atlanta approach macon sector but before I did that; there were two pieces of traffic that I decided to call to the pilot. The first was an aircraft on the boundary with my sector and atl approach that was at 070 that I believe I was talking to and the second aircraft was a VFR target just inside atlanta approaches airspace over the vna VOR converging with aircraft X indicating about 064. My intention was to call the traffic and then switch the aircraft to the next sector who had the hand off so they they could have enough time to call traffic since the conflict was slightly inside their airspace. So that's what I did; I called both pieces of traffic to the pilot and then switched him but the pilot asked again about where the traffic was and seemed confused so I had to spend more time to explain where the traffic was to the pilot. As the situation developed I decided it would be more prudent to call atl approach and coordinate something so that this aircraft won't hit this VFR aircraft that I see out there. When I called the atl controller to work something out; the other controller said something along the lines of; 'just ship him to me; I'll call the traffic to him again; that aircraft is VFR anyway.' I said I'm going to turn aircraft X 15L so the two aircraft don't hit.' the other controller said; 'that's fine; do what you want.' I turned aircraft X 15L to avoid the VFR traffic. In the mean time; the VFR target started a descent from 064 passed through 060; the same altitude as aircraft X. I my opinion; the 15L I gave aircraft X possibly avoided a collision. This situation was frustrating to me because we are constantly briefed here at ZJX that VFR aircraft are airplanes too; an although there is no specific separation minima between a VFR and a IFR; we still have an obligation to separate them to avoid a collision. The controller at atl approach had an indifferent; attitude about separating the IFR aircraft from the VFR aircraft. I'm sure that controller would have preferred to have been talking to aircraft X sooner but I was delayed shipping him because he kept asking questions about where the traffic I called was; so I decided to take matters into my own hands to avoid a collision even though the event happened just inside their airspace. That controller had the 'old school' mentality of; 'we'll he's VFR'.
Original NASA ASRS Text
Title: ZJX Controller describes a situation with tow aircraft that are at the same altitude and he needs to ship one to the next facility. He issues a 15 degree turn to the left and then ships the aircraft. Controller states the turn did help because the other aircraft descended to the turned aircraft's altitude.
Narrative: I was about to switch Aircraft X to Atlanta approach Macon sector but before I did that; there were two pieces of traffic that I decided to call to the pilot. The first was an aircraft on the boundary with my sector and ATL approach that was at 070 that I believe I was talking to and the second aircraft was a VFR target just inside Atlanta approaches airspace over the VNA VOR converging with Aircraft X indicating about 064. My intention was to call the traffic and then switch the aircraft to the next sector who had the hand off so they they could have enough time to call traffic since the conflict was slightly inside their airspace. So that's what I did; I called both pieces of traffic to the pilot and then switched him but the pilot asked again about where the traffic was and seemed confused so I had to spend more time to explain where the traffic was to the pilot. As the situation developed I decided it would be more prudent to call Atl Approach and coordinate something so that this aircraft won't hit this VFR aircraft that I see out there. When I called the ATL controller to work something out; the other controller said something along the lines of; 'Just ship him to me; I'll call the traffic to him again; that aircraft is VFR anyway.' I said I'm going to turn Aircraft X 15L so the two aircraft don't hit.' The other controller said; 'That's fine; do what you want.' I turned Aircraft X 15L to avoid the VFR traffic. In the mean time; the VFR target started a descent from 064 passed through 060; the same altitude as Aircraft X. I my opinion; the 15L I gave Aircraft X possibly avoided a collision. This situation was frustrating to me because we are constantly briefed here at ZJX that VFR aircraft are airplanes too; an although there is no specific separation minima between a VFR and a IFR; we still have an obligation to separate them to avoid a collision. The controller at ATL Approach had an indifferent; attitude about separating the IFR aircraft from the VFR aircraft. I'm sure that controller would have preferred to have been talking to Aircraft X sooner but I was delayed shipping him because he kept asking questions about where the traffic I called was; so I decided to take matters into my own hands to avoid a collision even though the event happened just inside their airspace. That controller had the 'old school' mentality of; 'We'll he's VFR'.
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.