 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Military aircraft entered adjacent ARTCC radar controller's airspace without proper coordination of flight plan.
| Attributes | |
| ACN | 148851 |
| Time | |
| Date | 199006 |
| Day | Tue |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | atc facility : gzg |
| State Reference | VA |
| Altitude | msl bound lower : 6000 msl bound upper : 6000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : ztl tracon : roa |
| Operator | other |
| Make Model Name | Fighter |
| Flight Phase | cruise other |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | oversight : supervisor |
| Qualification | controller : radar |
| ASRS Report | 148851 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : approach |
| Qualification | controller : radar |
| Experience | controller radar : 6 |
| ASRS Report | 148842 |
| Events | |
| Anomaly | non adherence : published procedure other anomaly other |
| Independent Detector | other controllera |
| Resolutory Action | none taken : detected after the fact |
| Consequence | Other |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Deviation |
Narrative:
Fgt IFR at 6000' ntu..sbv..PSK35015..GZG06414..hmv fpr ntw. The computer strip showed this flight plan was sent to ind ARTCC. We had 2 flight plans with 2 different beacon code assignments the aircraft was NORDO (no radio contact). I took a radar handoff from gso approach control. I called ind ARTCC and asked if he had the flight plan on fgt. He said 'yes', I said he had the flight plan on fgt. He said 'yes', I said block 6000' and gave the acfts position, 15 southeast psk at 6000' and squawking 2117. The aircraft was going into ind ARTCC's airspace. I tried to contact fgt, on 121.5 and 243.0. No contact was established. I removed the flight plan from dca's computer with the beacon code not being used by fgt. The aircraft entered atl's ARTCC's airspace and the atl controller had no flight plan and no coordination. Fgt called atl ARTCC on his frequency indicating that he did not have a radio failure. My air traffic manager, is insinuating that I might be remiss in not coordinating with both ind and atl artccs. I contend that I accomplished appropriate coordination with the receiving controller (ind ARTCC) and since I had no radio contact ind ARTCC would accept responsibility for successive coordination.
Original NASA ASRS Text
Title: MIL ACFT ENTERED ADJACENT ARTCC RADAR CTLR'S AIRSPACE WITHOUT PROPER COORD OF FLT PLAN.
Narrative: FGT IFR AT 6000' NTU..SBV..PSK35015..GZG06414..HMV FPR NTW. THE COMPUTER STRIP SHOWED THIS FLT PLAN WAS SENT TO IND ARTCC. WE HAD 2 FLT PLANS WITH 2 DIFFERENT BEACON CODE ASSIGNMENTS THE ACFT WAS NORDO (NO RADIO CONTACT). I TOOK A RADAR HDOF FROM GSO APCH CTL. I CALLED IND ARTCC AND ASKED IF HE HAD THE FLT PLAN ON FGT. HE SAID 'YES', I SAID HE HAD THE FLT PLAN ON FGT. HE SAID 'YES', I SAID BLOCK 6000' AND GAVE THE ACFTS POS, 15 SE PSK AT 6000' AND SQUAWKING 2117. THE ACFT WAS GOING INTO IND ARTCC'S AIRSPACE. I TRIED TO CONTACT FGT, ON 121.5 AND 243.0. NO CONTACT WAS ESTABLISHED. I REMOVED THE FLT PLAN FROM DCA'S COMPUTER WITH THE BEACON CODE NOT BEING USED BY FGT. THE ACFT ENTERED ATL'S ARTCC'S AIRSPACE AND THE ATL CTLR HAD NO FLT PLAN AND NO COORD. FGT CALLED ATL ARTCC ON HIS FREQ INDICATING THAT HE DID NOT HAVE A RADIO FAILURE. MY AIR TFC MGR, IS INSINUATING THAT I MIGHT BE REMISS IN NOT COORDINATING WITH BOTH IND AND ATL ARTCCS. I CONTEND THAT I ACCOMPLISHED APPROPRIATE COORD WITH THE RECEIVING CTLR (IND ARTCC) AND SINCE I HAD NO RADIO CONTACT IND ARTCC WOULD ACCEPT RESPONSIBILITY FOR SUCCESSIVE COORD.
Data retrieved from NASA's ASRS site as of July 2007 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.