A fractional flight crew reported the aircraft deviated off course on initial climb and flew below the Minimum Vectoring Altitude.

Date: 2025-09 · Aircraft: Challenger 650 · Phase: initial_climb

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

Synopsis

A fractional flight crew reported the aircraft deviated off course on initial climb and flew below the Minimum Vectoring Altitude.

Narrative

We departed XXR at ZZZ on the ZZZZZ departure ZZZ VOR transition in NAV mode. During the climb phase after ZZZ1 VOR; we turned past the initial 113° heading. ATC advised us that we were on a radar vector departure and were currently below the MVA and to climb to 4;000ft. We asked if they wanted us to make a right turn back to 113°. ATC responded no; to fly heading 340° and climb to 15;000ft. The next controller turned us right; direct ZZZ VOR. After our dual route verification; during my take off and departure briefing I briefed the PIC; who would be PM that I would depart in NAV mode and ask for Vertical Speed at ZZZ1 VOR. Soon after we received our CPDLC clearance and accepted it. Very soon after that we received a second CPDLC clearance and both verified that it was the same as the first one and accepted that one as well. What I believe happened is by accepting the second CPDLC clearance our programmed departure got dropped from the FMS. I still am unsure why we received a duplicate CPDLC clearance after accepting the original one. A possibility is that being rereleased due to not having ferry passengers may have triggered it.Suggestions: To prevent this from occurring we could have possibly declined the second CPDLC clearance to keep our departure from being dropped from the FMS. Additionally we could have dual verified that the second CPDLC contact did not drop the departure from the FMS. Finally; during our before take off brief; I confirmed ZZZ VOR as our first fix because it was fresh in my mind as it was in our clearance and was different than what our filed planned so I remembered verifying that change. However; if I compared that to the against the departure chart I would have caught that ZZZ VOR was not the first fix and realized the departure had dropped from the FMS.

Second reporter narrative

After manually entering our flight plan with a departure procedure. We dual verified the entire route including the ZZZZZ departure ZZZ VOR transition. Originally we had 2 company pax (Passengers) who did not show. Called and got re-released. We briefed to takeoff in nav mode to follow the departure. Approximately 500 ft the flight director commanded to start a left turn. During our left turn ATC advised we were supposed to be on a 113 heading for radar vectors. We asked if we should turn back to that heading but ATC told us to expedite through 3000 ft. Passing 3000 ft ATC gave us a heading of 340 all during visual flight conditions Suggestions: Being a long flight with multiple points and equal time points to enter we entered the flight plan as per the filed flight plan duel verification was done at that time. We received our clearance per CPDLC with a mod to insert that included the departure procedure we inserted the mod and dual verified the added points. We then received another CPDLC clearance that was identical to the 1st clearance we accepted the 2nd clearance because it was the same. Which in turn erased the departure procedure we entered into the flight plan without us catching it. We think a second clearance was issued because the no show pax and re-release. The lesson learned is to do another dual verification anytime a new clearance is issued even if it appears identical to the first one. I think that we would have caught our error had we verified the route again.

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