SkyWest Airlines Flight 5069
Mitsubishi CL-600-2B19 · Incident: runway excursion during landing
From Victoria Regional Airport (VCT) to George Bush Intercontinental Airport (IAH)
Event
- NTSB case
- DCA22LA182
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Incident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Mitsubishi CL-600-2B19
- Aircraft type
- Mitsubishi CL-600
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N965SW
- Operator
- SkyWest Airlines
- Onboard fatalities
- Unknown
- Route
- From Victoria Regional Airport (VCT), Victoria, TXTo George Bush Intercontinental Airport (IAH), Houston, TX
- Aircraft age
- About 19 years (built 2003)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 121: Air Carrier
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · landing roll
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Runway excursion
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Aircraft › Aircraft oper/perf/capability
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
After a normal touchdown and initial deceleration, the airplane tracked the runway heading before beginning a right turn to exit on a high-speed taxiway. The flight data recorder (FDR) revealed that, as the right turn developed, the captain released the brakes and the cockpit voice recorder (CVR) revealed that the captain commented about the lack of nosewheel steering. The captain applied full left rudder and used the nosewheel steering tiller but was unable to arrest the right turn, which continued but at a slightly reduced rate, until the airplane departed the paved surface and came to a full stop in the grass to the right of taxiway NK. During the excursion the airplane struck an airport sign and sustained minor damage to the right wing flap skin and fairing. Neither the tiller control input nor the nosewheel steering (NWS) angle were recorded by the FDR.
The thrust reversers remained deployed throughout the turn with a slight asymmetry. Although this would have provided some right-turning tendency, lateral control can be maintained with one engine at idle and the other at maximum reverse thrust using rudder and differential braking. The wind gusts recorded at the airport at the time of the incident could have produced a right crosswind component up to 15 knots. Given the airplane’s crosswind component limitation of 27 knots, the slight thrust asymmetry or crosswind component would not have rendered the airplane uncontrollable.
Post-incident testing of NWS components revealed no anomalies that would have precluded normal operation of the system. However, the handwheel control unit (tiller) failed the initial return-to center acceptance test. It was then cleaned, retested and passed. Although the FDR recorded a Nose Wheel Steer Status “FAIL/Not Armed” condition, and the crew observed a “STEERING INOP” message on the engine indicating and crew alerting system display, both of those messages occurred after the airplane departed the runway. The cause of these indications could not be determined. One possible condition that would have caused these indications was rapid tiller inputs, but the investigation could not assess those inputs because they were not recorded on the FDR.
Several fault codes were recovered from the NWS electronic control unit (ECU). Although these codes have no date or timestamp, they are stored chronologically. The most recent code recorded was “PILOT_HANDWHEEL_RATE_FAULT,” which, according to the type certificate holder’s Fault Isolation Manual, can occur if (1) the handwheel (tiller) is moved too rapidly or (2) the handwheel is moved (or was in a position) too far from center immediately after the extension of the landing gear. While it is likely that at least one code would have been logged on the ECU due to the recorded “FAIL/Not Armed” condition captured by the FDR, had this been the only code associated with the event, it alone, nor its potential causes, can explain the loss of lateral control. The FDR recorded “FAIL/Not Armed” condition occurred after the airplane departed the runway and may have been caused by the captain’s tiller inputs, or erratic nosewheel movement due to the excursion. Neither of which could be confirmed or refuted.
Given that the airplane initially tracked along the runway heading immediately after landing, it is unlikely that the nose landing gear steering angle would have been off center before or upon touchdown. The pilot used some differential braking to counter the right turn, though not to the fullest extent available. The pilot’s left rudder applications, which would have been less effective as the speed decreased, should have also commanded the nosewheel to turn up to 7° to the left of the airplane’s centerline. The pilot reported that he also used the tiller in an attempt to arrest the right turn, though a lack of recorded data precluded a determination of when and how much tiller command was applied. Post accident maintenance evaluation of the nosewheel steering system by the operator and subsequent component testing at manufacturers’ facilities found no evidence of malfunctioning or inoperative components. The cause of the right turn and why the pilot’s inputs were insufficient to arrest it, could not be determined.
Probable cause
A lateral runway excursion during landing for reasons that could not be determined based on the available evidence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA22LA182
- Event ID
- 20220816105749
- Case number
- DCA22LA182
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 6f99dc41ff97f3a482f62f608aa6d7e62ca1bca7de1cccc593e42a135baadf01; retrieved 2026-09-16T15:43:46.177Z.