Corporate jet flight crew reported a track heading deviation resulting in a CFTT event during departure from VNY airport.

Date: 2024-02 · Aircraft: Light Transport; Low Wing; 2 Turbojet Eng · Phase: climb

Anomalies: aircraft-equipment-problem-less-severe|deviation-track-heading-all-types|deviation-discrepancy-procedural-clearance|deviation-discrepancy-procedural-published-material-policy|inflight-event-encounter-cftt-cfit

Synopsis

Corporate jet flight crew reported a track heading deviation resulting in a CFTT event during departure from VNY airport.

Narrative

We are not frequent to VNY airport so we looked over the departure numerous times to ensure we knew all of climb and turn restrictions. We loaded the departure into the FMS and were departing in heading (HDG)/NAV mode with an initial climb to 4000 ft. On departure we complied with the 2 initial climb restrictions to PPRRY intersection. At PPRRY intersection the departure calls for a turn to 110 HDG. The heading was verified and in the FMS. We were still climbing relatively slowly due to the level off of 4000 ft. As the airplane was turning it the FMS continued passed the 110 heading to about 090 as if it was going to head to BSHOW intersection. At this point I pulled the chart to double check whether we missed something on the departure originally. The FMS still indicated the 110 HGD. As I was verifying the First Officer was running the after takeoff checklist. ATC came on and said to turn back to 110 HDG and expedite climb. I immediately followed ATC instructions and we were quickly above the MVA. We were in VMC conditions and terrain was not a factor; however after talking with ATC later they indicated altitude was the main concern with us not having climbed to the MVA yet. After several times looking and reviewing what we could have done different; when the FMS continued through what I originally thought and knew was the hdg per the chart; I should have promptly verified with ATC what heading they would like me to fly and/or as for a vector. Prompt communication is key in working together with ATC and I am certain they would have been happy to assist. In addition; we could have waited until we were higher to run the after takeoff checklist.

Second reporter narrative

The Captain and I Briefed the departure using our onboard jeppesen charts after completion of the brief we cross Checked waypoints and altitudes With the FMS and They matched with the chart. After takeoff and upon engaging the autopilot the plane began a premature turn; shortly after the Captain realized the plane began a turn off course we once again reviewed the departure for accuracy and began corrective action when at the same time ATC advised us of a low altitude alert advised a climb and a new heading. After discussing the events as a crew we came up with a couple solutions that would prevent this from happening again. 1st is while we brief to include a look at the charts in this case the chart did a better job at depicting the departure. 2nd would be to delay checklist usage by the pilot monitoring on takeoff as this would improve Situational Awareness.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.