 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZOA oceanic controller describes situation where he knows there should be an aircraft; attempts to track down the aircraft through another center. The other center knows nothing about the aircraft. The oceanic supervisor finds the aircraft; and the controller does not advise the other center of the aircrafts position.
| Attributes | |
| ACN | 1194036 |
| Time | |
| Date | 201408 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZOA.ARTCC |
| State Reference | CA |
| Environment | |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | Military Transport |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Cruise |
| Route In Use | None |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute Oceanic |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 1 |
| Events | |
| Anomaly | Airspace Violation All Types Deviation - Procedural Clearance |
Narrative:
I was working OC3 and received a message in the error queue regarding aircraft X en route from scel (santiago; chile) to kriv. The aircraft was attempting cpdlc log on to kzak without success and made an HF position report through [commercial radio.] aircraft X was estimating 28n120w at XX00Z then direct ficky. There was no flight plan in the system and I called ZLA under direction from the supervisor and inquired if they had any information on the aircraft. ZLA did not have information on the aircraft and I hung up. I placed a range bearing line between the two fixes and it skirted OC3 airspace. I did not receive a transfer from mazatlan center and aircraft X was flying in uncontrolled airspace. The supervisor found a flight plan in the acer and stated he was flying up the coast through uncontrolled airspace. At that point; I deleted the messages and took no further action.a) I recommend that aircraft do not fly though uncontrolled airspace.B) I should have called [commercial radio] to confirm this aircraft's route of flight.C) I should have called ZLA back and forwarded pertinent information (call sign; fix; time; altitude) and had them block the airspace until aircraft X was radar identified.
Original NASA ASRS Text
Title: ZOA Oceanic Controller describes situation where he knows there should be an aircraft; attempts to track down the aircraft through another Center. The other Center knows nothing about the aircraft. The Oceanic Supervisor finds the aircraft; and the controller does not advise the other Center of the aircrafts position.
Narrative: I was working OC3 and received a message in the Error Queue regarding Aircraft X en route from SCEL (Santiago; Chile) to KRIV. The aircraft was attempting CPDLC log on to KZAK without success and made an HF position report through [Commercial Radio.] Aircraft X was estimating 28N120W at XX00Z then direct FICKY. There was no flight plan in the system and I called ZLA under direction from the supervisor and inquired if they had any information on the aircraft. ZLA did not have information on the aircraft and I hung up. I placed a range bearing line between the two fixes and it skirted OC3 airspace. I did not receive a transfer from Mazatlan Center and Aircraft X was flying in uncontrolled airspace. The supervisor found a flight plan in the ACER and stated he was flying up the coast through uncontrolled airspace. At that point; I deleted the messages and took no further action.A) I recommend that aircraft do not fly though uncontrolled airspace.B) I should have called [Commercial Radio] to confirm this aircraft's route of flight.C) I should have called ZLA back and forwarded pertinent information (call sign; fix; time; altitude) and had them block the airspace until Aircraft X was radar identified.
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.