37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1051445 |
Time | |
Date | 201211 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | JAX.TRACON |
State Reference | FL |
Aircraft 1 | |
Make Model Name | SR22 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | S-70/UH-60 Blackhawk/Seahawk/Pavehawk/Knighthawk |
Flight Phase | Final Approach |
Flight Plan | IFR |
Person 1 | |
Function | Approach Departure |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
I was working aircraft X from the southwest for an ILS to crg. I asked nrb radar who was working aircraft Y; to keep the pattern tight so I could follow with my approach to crg. I asked the pilot to reduce his speed for sequence. Both crg and nrb airports were VFR with low ceilings. Our letter of agreement states that crg tower will provide visual separation when the field is VFR; unless the tower states otherwise. The final to nrb crosses over crg tower; and in this case the aircraft was vectored out a little further than I anticipated. I knew it was going [to] get close; but I figured that nrb would point-out the helicopter to crg tower; in turn crg tower would be talking to aircraft X on final to runway 32 to circle to runway 5. My instinct was to verify with crg that they could provide visual separation; and the tower's response was that they were both above the bases of the clouds and they could not see them. I immediately called crg tower back and told him to break the aircraft out. I assigned a heading of 210 and 3;000 ft altitude. By the time crg tower got the aircraft turned; they seemed to have gotten close. Nrb aircraft doing a gca approach to runway 5 is a conflict with aircraft doing practically any approach at crg. The airports are just in close proximity to each other; and it's always a hand-full. Also; be more mindful of the bases in the future; and realize that crg tower might not be able to give the visual separation they are required due to weather.
Original NASA ASRS Text
Title: JAX TRACON Controller described a loss of separation event when anticipated visual separation could not be provided by CRG Tower.
Narrative: I was working Aircraft X from the southwest for an ILS to CRG. I asked NRB RADAR who was working Aircraft Y; to keep the pattern tight so I could follow with my approach to CRG. I asked the pilot to reduce his speed for sequence. Both CRG and NRB airports were VFR with low ceilings. Our Letter of Agreement states that CRG Tower will provide visual separation when the field is VFR; unless the Tower states otherwise. The final to NRB crosses over CRG Tower; and in this case the aircraft was vectored out a little further than I anticipated. I knew it was going [to] get close; but I figured that NRB would point-out the helicopter to CRG Tower; in turn CRG Tower would be talking to Aircraft X on final to Runway 32 to circle to Runway 5. My instinct was to verify with CRG that they could provide visual separation; and the Tower's response was that they were both above the bases of the clouds and they could not see them. I immediately called CRG Tower back and told him to break the aircraft out. I assigned a heading of 210 and 3;000 FT altitude. By the time CRG Tower got the aircraft turned; they seemed to have gotten close. NRB aircraft doing a GCA approach to Runway 5 is a conflict with aircraft doing practically any approach at CRG. The airports are just in close proximity to each other; and it's always a hand-full. Also; be more mindful of the bases in the future; and realize that CRG Tower might not be able to give the visual separation they are required due to weather.
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.