37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1575634 |
Time | |
Date | 201809 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZOA.ARTCC |
State Reference | CA |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Gulfstream G100/G150 (IAI 1125 Astra) |
Operating Under FAR Part | Part 91 |
Flight Phase | Climb |
Route In Use | None |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | B787-900 |
Operating Under FAR Part | Part 129 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Developmental |
Events | |
Anomaly | Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
I received a message from aircraft Y relaying a message from aircraft X stating that the aircraft had departed ptpn VFR; was leaving FL230 climbing to FL400; and was requesting an IFR clearance to rpmd. I replied to aircraft Y to relay to aircraft X the HF frequencies and to contact [commercial radio] for IFR clearance and provide present position latitude/longitude and altitude. I told aircraft to maintain VFR. I contacted [commercial radio] and asked if they had communication with aircraft X. They advised they could hear the pilot but he couldn't hear them. I then received another message from aircraft Y relaying aircraft X position report; level at FL400; and still requesting IFR clearance. I used a brasher warning to aircraft X; relayed through aircraft Y. Aircraft X called the supervisor on the landline and I was able to issue IFR clearance at that time. At the time I received the message that aircraft X was leaving FL230 climbing to FL400; the aircraft was in conflict with aircraft Y at FL370. Aircraft X climbed to FL400 without an IFR clearance and caused possible loss of separation with aircraft Y. A course of action I could/should have taken was to advise both aircraft of the situation and attempted to stop aircraft X climb by issuing a lower altitude. I advised the aircraft to maintain VFR in hopes the aircraft would descend and remain below FL200; which is VFR airspace as prescribed in the pac chart supplement.
Original NASA ASRS Text
Title: Oakland Oceanic Controller reported a loss of separation between two aircraft.
Narrative: I received a message from Aircraft Y relaying a message from Aircraft X stating that the aircraft had departed PTPN VFR; was leaving FL230 climbing to FL400; and was requesting an IFR clearance to RPMD. I replied to Aircraft Y to relay to Aircraft X the HF frequencies and to contact [Commercial Radio] for IFR clearance and provide present position latitude/longitude and altitude. I told aircraft to maintain VFR. I contacted [Commercial Radio] and asked if they had communication with Aircraft X. They advised they could hear the pilot but he couldn't hear them. I then received another message from Aircraft Y relaying Aircraft X position report; level at FL400; and still requesting IFR clearance. I used a brasher warning to Aircraft X; relayed through Aircraft Y. Aircraft X called the Supervisor on the landline and I was able to issue IFR clearance at that time. At the time I received the message that Aircraft X was leaving FL230 climbing to FL400; the aircraft was in conflict with Aircraft Y at FL370. Aircraft X climbed to FL400 without an IFR clearance and caused possible loss of separation with Aircraft Y. A course of action I could/should have taken was to advise both aircraft of the situation and attempted to stop Aircraft X climb by issuing a lower altitude. I advised the aircraft to maintain VFR in hopes the aircraft would descend and remain below FL200; which is VFR airspace as prescribed in the PAC Chart Supplement.
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.