Challenger 350 flight crew reported a loss of directional control during the take-off roll. The pilots rejected the take-off and returned to the FBO.

2022-12 · NASA ASRS report 1958413

Date: 2022-12 · Aircraft: Challenger 350 · Phase: takeoff

Anomalies: ground-event-encounter-weather-turbulence|ground-event-encounter-loss-of-aircraft-control

Synopsis

Challenger 350 flight crew reported a loss of directional control during the take-off roll. The pilots rejected the take-off and returned to the FBO.

Narrative

Our flight blocked out and proceeded to the de-icing pad. The weather was winds 050 at 14 kts; 1 ½ miles visibility; light snow; and braking action. Once de-icing procedures were completed; we continue taxiing for a Runway XX departure. Once we received our take-off clearance and completed all checklist; we lined up for departure. I observed the Pilot Flying; the First Officer (FO) slowly advancing the throttles to take-off power and we began take-off roll. The FO had the yoke turned into the wind for crosswind control. I the Non-Flying; pilot call 'power set'; as we began to accelerate; I called 'airspeed alive'; and all operations were normal and maintaining a center line track. I made the 80 kt. call out and was confirmed by the FO. Moments later the aircraft began to veer to the left; at approximately 2000 ft. down the runway. At this point the FO began to put inputs to maintain center line alignment. Realizing the continued input were not helping and we were unable to maintain directional control; we initiated an aborted take-off. At this time the aircraft continued move toward the left edge of the runway. The FO continued to attempt to regain control. As we were on the left edge of the runway; the FO was able to gain minimal directional control that kept the aircraft from exiting the runway. Once the aircraft was under control; we came to a stop; advised the Control Tower we aborted take-off due to loss of directional control. We exited the runway via the taxiway; completed the rejected take-off and after landing checks; then taxied back to parking.

Second reporter narrative

We initiated a take-off on Runway XX at ZZZ. The reported weather at the time had winds of 050 at 14 kts; visibility of 1.5 miles with light snow. Runway braking action was reported as 3/3/3. We had just completed ground deice and anti-ice procedures and experienced no delays in our taxi to the runway. During the taxi; we completed all required checklist. As we were taxiing; ground crews were performing contamination removal procedures of the runway. At this time; directional control and braking were normal. As we neared the Runway XX for departure; we received our take-off clearance. As the Pilot Flying; I called for the runway lineup checklist. As the Non-Flying pilot; the Captain completed the checklist and announced that it was complete. At this point we had no indication of any faults with the aircraft. Next; I slowly advanced the power levers; applied crosswind corrections and called for the Captain to set take-off power to which Captain replied 'power set.' The aircraft tracked center line and accelerated normally. The Captain then stated; 'airspeed alive.' Captain then made the 80 kts. call out which I confirmed. Shortly after this; about 2000 ft. down the runway; the aircraft began to veer to the left. I slowly decreased crosswind control and applied right rudder in an attempt to maintain center line. The plane continued to the edge of the runway. It was at this point that I realized that I did not have control of the aircraft and I initiated the abort. We continued toward the edge of the runway and I was able to keep the right main landing gear on the pavement as we tracked down the runway for approximately 2000 ft. We crossed the intersection of taxiway X and I was able to slowly bring the aircraft back to center line; regain control; and came to a stop. We advised Tower that we had aborted the take-off due to a loss of directional control and that we needed to return to the FBO ramp. Upon clearing the runway; we completed the rejected take-off checklist and after landing checks. We checked with our Flight Attendant (FA) to ensure our passengers were ok. After parking on the ramp; we completed a shutdown check.

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

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

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.

Which aircraft types can I filter by?

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.

Is FlightFinder free to use?

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.

Where does the route data come from?

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.