Narrative:

After preparing the aircraft for departure; the pilot not flying (PNF) was conducting a cockpit brief. During the briefing an ATC message/alert (cyan) was displayed on the cas stack; indicating that the cpdlc dcl (controller-pilot data link communication departure clearance) had been issued. Pausing the cockpit brief; the PNF opened the departure clearance only to see that it was an FMS flight plan reroute. After inserting the 'mod' into the FMS and verifying the waypoints; the modified route was accepted. The PNF then noticed that the clearance also included a new SID (standard instrument departure/ZZOOO1.ipl); but the modified route that was inserted did not contain that SID. Upon manually selecting the runway and ZZOOO1 SID and entering it into the FMS; the PNF reviewed the SID waypoints and altitudes and noticed that the first waypoint (jetti) on the SID was not included in the FMS entry. After rechecking that the correct runway (runway 27) was selected on the departure page; the PNF manually entered the missing SID waypoint along with its associated altitude.shortly after this took place; the 14 passengers and baggage arrived at the aircraft. The PNF left the cockpit and proceeded to the back of the aircraft to load the baggage and then assist with greeting the passengers. Once they were settled; the PNF returned to the cockpit to join the PF and the start check was immediately initiated. On departure the aircraft departed on runway heading; navigation was selected and the aircraft proceeded to fly towards the first waypoint on the SID. Short of this waypoint; the aircraft began its left turn towards the next waypoint on the departure; failing to overfly this 'flyover' waypoint. This 'flyover' designation of this waypoint was missed and not thought of until further on the departure when ATC asked the aircraft to call socal (southern california TRACON) when able; forcing a review of the departure procedure. Once at cruise; the crew attempted to see if this 'missing waypoint' could be repeated. A secondary flight plan was begun and when runway 27 and the ZZOOO1.ipl was selected; all the waypoints in the SID were present (including the waypoint jetti; which was not present in the initial selection). The PNF then attempted to call socal on the satcom; but was unable to get a connection. Upon arrival at destination; the PNF tried an additional 14 times to call socal; getting a busy signal each time. The aircraft subsequently departed to fly to a new destination. Upon reaching that destination; the PNF again made more 4 attempts to call socal; each attempt getting a busy signal. Upon landing back at our base of operations the chief pilot was briefed on the event and the PNF spoke to san diego TRACON and resolved the issue.

Google
 

Original NASA ASRS Text

Title: Corporate jet Captain reported that a CPDLC modification of the SAN SID had to be manually entered. A flyover waypoint was not noted which caused the aircraft to turn early.

Narrative: After preparing the aircraft for departure; the Pilot Not Flying (PNF) was conducting a cockpit brief. During the briefing an ATC MSG/ALERT (cyan) was displayed on the CAS stack; indicating that the CPDLC DCL (Controller-Pilot Data Link Communication Departure Clearance) had been issued. Pausing the cockpit brief; the PNF opened the departure clearance only to see that it was an FMS flight plan reroute. After inserting the 'MOD' into the FMS and verifying the waypoints; the modified route was accepted. The PNF then noticed that the clearance also included a new SID (Standard Instrument Departure/ZZOOO1.IPL); but the modified route that was inserted did not contain that SID. Upon manually selecting the runway and ZZOOO1 SID and entering it into the FMS; the PNF reviewed the SID waypoints and altitudes and noticed that the first waypoint (JETTI) on the SID was not included in the FMS entry. After rechecking that the correct runway (RWY 27) was selected on the departure page; the PNF manually entered the missing SID waypoint along with its associated altitude.Shortly after this took place; the 14 passengers and baggage arrived at the aircraft. The PNF left the cockpit and proceeded to the back of the aircraft to load the baggage and then assist with greeting the passengers. Once they were settled; the PNF returned to the cockpit to join the PF and the START Check was immediately initiated. On departure the aircraft departed on runway heading; NAV was selected and the aircraft proceeded to fly towards the first waypoint on the SID. Short of this waypoint; the aircraft began its left turn towards the next waypoint on the departure; failing to overfly this 'flyover' waypoint. This 'flyover' designation of this waypoint was missed and not thought of until further on the departure when ATC asked the aircraft to call SOCAL (Southern California TRACON) when able; forcing a review of the departure procedure. Once at cruise; the crew attempted to see if this 'missing waypoint' could be repeated. A secondary flight plan was begun and when RWY 27 and the ZZOOO1.IPL was selected; all the waypoints in the SID were present (including the waypoint JETTI; which was not present in the initial selection). The PNF then attempted to call SOCAL on the SATCOM; but was unable to get a connection. Upon arrival at destination; the PNF tried an additional 14 times to call SOCAL; getting a busy signal each time. The aircraft subsequently departed to fly to a new destination. Upon reaching that destination; the PNF again made more 4 attempts to call SOCAL; each attempt getting a busy signal. Upon landing back at our base of operations the Chief Pilot was briefed on the event and the PNF spoke to San Diego TRACON and resolved the issue.

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.