37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1750417 |
Time | |
Date | 202007 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | SFO.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | Light Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 135 |
Flight Phase | Climb |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
Filed route out of sfo included ...syrah oal J58 ilc... Arinc flight plan was downloaded into the FMS and all points checked; waypoints were ...syrah TOC oal ilc... Pre departure clearance clearance amended only this section of the flight plan to ...syrah Q128 jsica ilc... Pilot flying downloaded/opened the 'scheduled flight' plan in foreflight and the routing matched the ATC (pre departure clearance) assigned routing. Pilot flying looked at the routing on the jepp high altitude chart and saw it only involved one waypoint between syrah and ilc; so they replaced oal with jsica. Pilot flying backed up in the flight plan in the FMS and verified the points from the end of the dp at syrah through rejoining the filed flight plan at ilc; they were syrah TOC jsica ilc. During the departure brief; both pilots acknowledged the change in the pre departure clearance; both pilots reviewed the amended section of waypoints in the FMS. Shortly after passing syrah; ATC asked if we were proceeding to jsica; the pilot flying immediately realized they were proceeding to the TOC waypoint (which was on the original route to oal); but it was not on a direct line to jsica; and hit direct jsica; pilot monitoring responded they were now direct jsica. Checking position against forefllight; we were probably about 2.5 miles off the correct course between syrah and jsica when we corrected our heading. ATC had no further comments and the rest of the flight was uneventful. Arinc creating and adding superfluous waypoints (TOC/TOD) to our flight plans...and pilot data entry/review error.1) (arinc) not create imaginary waypoints (TOC/TOD) and add them to our FMS routing. 2) (crew) load the re-route using the extra button pokes of the airway name; even if there are no additional waypoints along the route. (This should have caused the FMS to delete the TOC waypoint-or reject the airway if entered after TOC.) 3) (crew) we could go to the map on the mfd and cycle through all the points till we reached the amended area and see where that one point we changed got plotted; that would have trapped the error as we would have seen the jink in the course caused by TOC; however; I'd argue that's not practical for a simple one fix correction; we were looking at the new course line in foreflight on the jepp high altitude chart and it looked good; and the fixes in the FMS matched those on the chart...except the extra made up point 'TOC' that I have become accustomed to ignoring. 4) (crew) be cognizant of the make up points TOC and TOD and delete them if they lie within or adjacent to any route changes.
Original NASA ASRS Text
Title: Fractional pilot reported a track deviation occurred when the flight crew failed to properly load the route in the FMC.
Narrative: Filed route out of SFO included ...SYRAH OAL J58 ILC... ARINC flight plan was downloaded into the FMS and all points checked; waypoints were ...SYRAH TOC OAL ILC... PDC clearance amended only this section of the flight plan to ...SYRAH Q128 JSICA ILC... Pilot Flying downloaded/opened the 'scheduled flight' plan in ForeFlight and the routing matched the ATC (PDC) assigned routing. Pilot Flying looked at the routing on the Jepp High Altitude chart and saw it only involved one waypoint between SYRAH and ILC; so they replaced OAL with JSICA. Pilot Flying backed up in the flight plan in the FMS and verified the points from the end of the DP at SYRAH through rejoining the filed flight plan at ILC; they were SYRAH TOC JSICA ILC. During the departure brief; both pilots acknowledged the change in the PDC; both pilots reviewed the amended section of waypoints in the FMS. Shortly after passing SYRAH; ATC asked if we were proceeding to JSICA; the Pilot Flying immediately realized they were proceeding to the TOC waypoint (which was on the original route to OAL); but it was not on a direct line to JSICA; and hit Direct JSICA; Pilot Monitoring responded they were now direct JSICA. Checking position against ForeFllight; we were probably about 2.5 miles off the correct course between SYRAH and JSICA when we corrected our heading. ATC had no further comments and the rest of the flight was uneventful. ARINC creating and adding superfluous waypoints (TOC/TOD) to our flight plans...and pilot data entry/review error.1) (ARINC) Not create imaginary waypoints (TOC/TOD) and add them to our FMS routing. 2) (Crew) Load the re-route using the extra button pokes of the airway name; even if there are no additional waypoints along the route. (This should have caused the FMS to delete the TOC waypoint-or reject the airway if entered after TOC.) 3) (Crew) We could go to the map on the MFD and cycle through all the points till we reached the amended area and see where that one point we changed got plotted; that would have trapped the error as we would have seen the jink in the course caused by TOC; however; I'd argue that's not practical for a simple one fix correction; we were looking at the new course line in ForeFlight on the Jepp High Altitude chart and it looked good; and the fixes in the FMS matched those on the chart...except the extra made up point 'TOC' that I have become accustomed to ignoring. 4) (Crew) Be cognizant of the make up points TOC and TOD and delete them if they lie within or adjacent to any route changes.
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.