2011-11 · NASA ASRS report 977972
An Oceanic Controller enters a arrival time estimate with a ten hour typo from actual. When the aircraft contacts the receiving radar controller; the problem is identified. Controllers noted that the ATOPS system checks many parameters but not this one.
Aircraft X initiated contact. As per standard operating procedure; I looked for the corresponding flight strip in order to assign the flight a beacon code. When I did not find the flight strip; I requested the flight plan from HOST and discovered that the flight plan was not stored in HOST. I requested a beacon code from HOST and assigned it to Aircraft X. After positively radar identifying the aircraft; I proceeded to type in Aircraft X's flight plan. From this point on; I worked the flight as a routine arrival. There was no loss of separation involving Aircraft X during this event. I subsequently found out that the cause of this event was a typographical error during input of Aircraft X's boundary estimate into the ATOP system. The ATOP Controller had inadvertently typed in an estimate that was ten hours later than what was intended to type (JX00 vs. AX00). There are currently numerous logic checks within the ATOP system concerning aircraft data such as weight category; cruising speed; ceiling altitude; etc. These logic checks; while not always correct; do have value as they draw attention to potential typographical and/or other errors. It is puzzling why there is not a logic check pertaining to boundary estimates. A logic check of boundary estimates would have drawn attention to the typographical error since facilities do not pass boundary estimates that are that far into the future.
Aircraft X was coordinated northbound to me at flight level 360 to enter my airspace at AX20Z. I inadvertently entered a time of JX20Z. Subsequently there were reports made by the aircraft which appeared to be incorrect because of this time disparity. The aircraft traversed the airspace without being in conflict with any other aircraft and was observed approaching the radar sector north of mine where he was radar identified and continued on to his destination.There were 2 primary causes for this event - the mistyped coordination message; and the subsequent misunderstood error messages. What absolutely needs to be changed is the ATOP system not giving some form of warning that there is a huge time discrepancy between what it expects for a time on an incoming aircraft and what is actually typed in. In numerous other cases; no matter how trivial; ATOP informs you; ad nauseum; of discrepancies; most notably speeds; altitudes and weight classes that it feels are incorrect. For example; an aircraft operating at FL400 that the system feels has a ceiling of FL390 will generate a special message which MUST be acknowledged every single time you interact with this aircraft - even though you have repeatedly acknowledged that yes; the airplane who says he is at FL400 is actually at FL400. Yet; when an aircraft is apparently 10 hours ahead of schedule; ATOP treats this exactly the same as if he is 4 minutes ahead of time.
More incidents for this aircraft family
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.