37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 828157 |
Time | |
Date | 200903 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZOA.ARTCC |
State Reference | CA |
Environment | |
Flight Conditions | IMC |
Aircraft 1 | |
Make Model Name | B757 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | B757 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Non Radar 1 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict |
Narrative:
During hnl rush; aircraft X and aircraft Y were transferred out. Aircraft X unaware to me had an amendment that changed the eloyi time from XA04Z to XA43Z causing the data block to jump back into hnl's airspace. Aircraft X was at FL370. Aircraft Y had progressed to oakland's airspace at XA11Z with a position report over eloyi. At XA14Z aircraft Y requested lower altitude down to FL350. With traffic at FL360; they were what appeared to be able FL370. I descended aircraft Y to FL370 at XA47Z. Confusion occurred when aircraft X started flashing overdue to eloyi; but when aircraft X was asked for position report; they reported over errot at XA50Z. Expecting a report over eloyi; I questioned the flight and had them confirm position. The position had in fact been errot. Once I had updated the correct position; I climbed aircraft Y up to FL380 and had regained separation at XA10Z. After looking through aircraft X aircraft messages; it appears that a message containing aircraft X's position report had been mistakenly deleted.
Original NASA ASRS Text
Title: ZOA Controller experienced operational error at FL370 during non radar oceanic procedures when failing to note an aircraft position report had inadvertently been deleted.
Narrative: During HNL rush; Aircraft X and Aircraft Y were transferred out. Aircraft X unaware to me had an amendment that changed the ELOYI time from XA04Z to XA43Z causing the data block to jump back into HNL's airspace. Aircraft X was at FL370. Aircraft Y had progressed to Oakland's airspace at XA11Z with a position report over ELOYI. At XA14Z Aircraft Y requested lower altitude down to FL350. With traffic at FL360; they were what appeared to be able FL370. I descended Aircraft Y to FL370 at XA47Z. Confusion occurred when Aircraft X started flashing overdue to ELOYI; but when Aircraft X was asked for position report; they reported over ERROT at XA50Z. Expecting a report over ELOYI; I questioned the flight and had them confirm position. The position had in fact been ERROT. Once I had updated the correct position; I climbed Aircraft Y up to FL380 and had regained separation at XA10Z. After looking through Aircraft X aircraft messages; it appears that a message containing Aircraft X's position report had been mistakenly deleted.
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.