 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZDC controller described a TCAS RA event involving an air carrier cleared through a military restricted area; apparently from an unreported/unknown airspace user.
| Attributes | |
| ACN | 965321 |
| Time | |
| Date | 201108 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZDC.ARTCC |
| State Reference | VA |
| Aircraft 1 | |
| Make Model Name | B737-700 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Hawkeye (E2) |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Climb |
| Route In Use | None |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | Conflict Airborne Conflict |
Narrative:
I was training on the r-side at sector 11. A B737; a departure from bwi; was at 14;000. Aircraft was minimum fuel. We coordinated direct stein intersection. We made a radar point to the patuxent restricted area complex 'baywatch'. The complex was active up to FL470. They approved the flight through the active military airspace. We noticed a mode C intruder about 10 miles southwest of the B737; the aircraft was turning and climbing towards the B737. We called baywatch to verify that they knew; they took a point out on our aircraft coming through their airspace. The controller's response was 'roger; we're trying to contact the aircraft'. We twice called the traffic; which was an E2; to the B737. We also stated we didn't know what the aircraft was doing; or whether baywatch had gotten in contact with the aircraft and/or what they were doing if they had. A few seconds later the B737called saying they were responding to a TCAS RA. The mode C readout jumped from level at 14;000 to 14;900 in one hit. I could not bring up that mode C intruder on the falcon replay. So I do not know how close the two aircraft were. Even if aircraft are 'playing' in an active military airspace; having communications with the aircraft inside the restricted area would be advantageous.
Original NASA ASRS Text
Title: ZDC Controller described a TCAS RA event involving an Air Carrier cleared through a Military Restricted Area; apparently from an unreported/unknown airspace user.
Narrative: I was training on the R-Side at Sector 11. A B737; a departure from BWI; was at 14;000. Aircraft was minimum fuel. We coordinated direct STEIN Intersection. We made a RADAR point to the Patuxent Restricted Area Complex 'Baywatch'. The complex was active up to FL470. They approved the flight through the active military airspace. We noticed a Mode C intruder about 10 miles southwest of the B737; the aircraft was turning and climbing towards the B737. We called Baywatch to verify that they knew; they took a point out on our aircraft coming through their airspace. The Controller's response was 'roger; we're trying to contact the aircraft'. We twice called the traffic; which was an E2; to the B737. We also stated we didn't know what the aircraft was doing; or whether Baywatch had gotten in contact with the aircraft and/or what they were doing if they had. A few seconds later the B737called saying they were responding to a TCAS RA. The Mode C readout jumped from level at 14;000 to 14;900 in one hit. I could not bring up that Mode C intruder on the Falcon replay. So I do not know how close the two aircraft were. Even if aircraft are 'playing' in an active military airspace; having communications with the aircraft inside the restricted area would be advantageous.
Data retrieved from NASA's ASRS site as of April 2012 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.