37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1334490 |
Time | |
Date | 201602 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZDC.ARTCC |
State Reference | VA |
Environment | |
Light | Night |
Aircraft 1 | |
Make Model Name | B777-200 |
Operating Under FAR Part | Part 129 |
Flight Phase | Cruise |
Route In Use | Direct |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Commercial Fixed Wing |
Flight Phase | Cruise |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 3.1 |
Events | |
Anomaly | ATC Issue All Types Conflict NMAC Deviation - Procedural Published Material / Policy |
Narrative:
Last night; I was informed that aircraft X was involved in a near midair collision.last night; I was working the radar position. At some point during the session; another sector initiated a handoff to me of aircraft X at 37;000 feet. Prior to taking the handoff I examined its route. I realized that route put the aircraft in conflict with a warning area.I figured that aircraft X was too heavy for 39;000 feet at the time; and rather than inconvenience the overseas flight; I decided to see if I could get the controlling agency for the warning area to approve the aircraft on its filed route through the warning area. From experience; I know that sometimes they assume separation responsibility (via pointout or handoff) for flights through active warning areas on specific routes or at specific altitudes. I was thinking that if they were able to take a pointout or handoff of aircraft X through the warning area I would not create an additional conflict within my airspace for aircraft X and the aircraft could remain on the most direct routing.I then initiated coordination to determine whether or not they could approve a pointout on aircraft X. They could not initially answer; they said they would call me back. I continued working and approximately a minute later they called me and told me they could assume separation responsibility (via pointout) for aircraft X through the warning area. My plan was to affect a handoff of the aircraft to a ZDC sector; as it transited a portion of their airspace prior to entering [the warning area]; and let them know that aircraft X was approved on his route.the warning area controlling agency agreed to take communications with aircraft X (accepting a handoff) and I switched aircraft X to them.I finished that session and went on break. I then worked another session and when I was relieved; my manager asked me if I knew what had happened with the aircraft X debacle. I remembered the flight and the details of the situation; but wasn't aware of an issue until he informed me that aircraft X had been involved in a near midair collision. I was not able to see what happened on the falcon; but I am told aircraft X received an RA while in the warning area.I take my duty as a controller very seriously; and I was very disheartened to know that aircraft X was placed in any potential danger as a consequence of my decision to allow the warning area controllers to assume separation responsibility for the flight. Though it is my understanding that they have the capability to provide separation for aircraft transiting airspace under their control; I will not trust them to do so in the future. It is probably much safer to simply route aircraft around their airspace to the extent practicable.
Original NASA ASRS Text
Title: A ZDC Controller received approval for an aircraft to fly through a Warning Area. While in the Warning Area the aircraft was involved in a NMAC and responded to an RA.
Narrative: Last night; I was informed that Aircraft X was involved in a NMAC.Last night; I was working the radar position. At some point during the session; another sector initiated a handoff to me of Aircraft X at 37;000 feet. Prior to taking the handoff I examined its route. I realized that route put the aircraft in conflict with a Warning Area.I figured that Aircraft X was too heavy for 39;000 feet at the time; and rather than inconvenience the overseas flight; I decided to see if I could get the controlling agency for the Warning Area to approve the aircraft on its filed route through the Warning Area. From experience; I know that sometimes they assume separation responsibility (via pointout or handoff) for flights through active warning areas on specific routes or at specific altitudes. I was thinking that if they were able to take a pointout or handoff of Aircraft X through the Warning Area I would not create an additional conflict within my airspace for Aircraft X and the aircraft could remain on the most direct routing.I then initiated coordination to determine whether or not they could approve a pointout on Aircraft X. They could not initially answer; they said they would call me back. I continued working and approximately a minute later they called me and told me they could assume separation responsibility (via pointout) for Aircraft X through the Warning Area. My plan was to affect a handoff of the aircraft to a ZDC Sector; as it transited a portion of their airspace prior to entering [the warning area]; and let them know that Aircraft X was approved on his route.The Warning Area controlling Agency agreed to take communications with Aircraft X (accepting a handoff) and I switched Aircraft X to them.I finished that session and went on break. I then worked another session and when I was relieved; my manager asked me if I knew what had happened with the Aircraft X debacle. I remembered the flight and the details of the situation; but wasn't aware of an issue until he informed me that Aircraft X had been involved in a NMAC. I was not able to see what happened on the Falcon; but I am told Aircraft X received an RA while in the Warning Area.I take my duty as a controller very seriously; and I was very disheartened to know that Aircraft X was placed in any potential danger as a consequence of my decision to allow the Warning Area controllers to assume separation responsibility for the flight. Though it is my understanding that they have the capability to provide separation for aircraft transiting airspace under their control; I will not trust them to do so in the future. It is probably much safer to simply route aircraft around their airspace to the extent practicable.
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.