37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1095445 |
Time | |
Date | 201306 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZJX.ARTCC |
State Reference | FL |
Aircraft 1 | |
Make Model Name | Regional Jet 700 ER/LR (CRJ700) |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Fighting Falcon F16 |
Flight Phase | Climb |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Person 2 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy |
Narrative:
AR600 was active 250b280; sector R47 was working the AR600 flights. The AR600 track also overlaps R66's airspace so I took a point out on all the aircraft in AR600. It was an extremely complex situation with weather deviations and AR600 active. I did have a d-side at the time when we loss separation; he advised me to watch a code and stop crj-700's climb to FL250 since we were unsure of what the F-16's intentions were. The F-16 was supposedly marsa with the kc-135; but the flight of 2 F16's deviated away from the kc-135's instructions. It appeared that the F-16s started following the crj-700 for some unknown reason. I originally climbed the crj-700 to FL240; then when I thought I had separation from AR600 I climbed the crj-700 to FL260; then we noticed that the F-16s turned to the west and were catching up to the crj-700; that is when my d-side told me to stop the crj-700 climb to FL250. My d-side and I were unaware that the F16s were a flight of 2; so we originally thought we had separation between the F-16s and the crj-700 aircraft. When there is weather; AR600 should be coordinated prior and management should make a decision if it is feasible or not to approve the activity. I also feel that tmu could have helped out with AR600 and the clt arrivals since there was weather and aircraft deviating all over the place.
Original NASA ASRS Text
Title: ZJX Controllers described a restricted area spill out resulting in a conflict event. The reporters claimed the airspace location is problematic and should be relocated.
Narrative: AR600 was active 250B280; Sector R47 was working the AR600 flights. The AR600 track also overlaps R66's airspace so I took a point out on all the aircraft in AR600. It was an extremely complex situation with weather deviations and AR600 active. I did have a D-Side at the time when we loss separation; he advised me to watch a code and stop CRJ-700's climb to FL250 since we were unsure of what the F-16's intentions were. The F-16 was supposedly MARSA with the KC-135; but the flight of 2 F16's deviated away from the KC-135's instructions. It appeared that the F-16s started following the CRJ-700 for some unknown reason. I originally climbed the CRJ-700 to FL240; then when I thought I had separation from AR600 I climbed the CRJ-700 to FL260; then we noticed that the F-16s turned to the west and were catching up to the CRJ-700; that is when my D-Side told me to stop the CRJ-700 climb to FL250. My D-Side and I were unaware that the F16s were a flight of 2; so we originally thought we had separation between the F-16s and the CRJ-700 aircraft. When there is weather; AR600 should be coordinated prior and management should make a decision if it is feasible or not to approve the activity. I also feel that TMU could have helped out with AR600 and the CLT arrivals since there was weather and aircraft deviating all over the place.
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.