FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN19LA054 · Canadair CL 600 2A12 601

12 Jan 2019 · Uvalde, TX, United States

Tw 601-C Investment Canadair CL 600 2A12 601 · Accident: hard landing

From Fort Worth Meacham International Airport (FTW) to Beulah Field (01TX)

Report a problem

Event

NTSB case
CEN19LA054
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
Accident
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
Unknown
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
General aviation
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

Canadair CL 600 2A12 601

Aircraft type
Canadair 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
N813WT
Onboard fatalities
Unknown
Route
From Fort Worth Meacham International Airport (FTW), Fort Worth, TXTo Beulah Field (01TX), Uvalde, TX
Aircraft age
About 36 years (built 1983)
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 91: General Aviation
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 · flare/touchdown
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
Hard landing
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot, copilot, flight attendant, and six passengers departed on a corporate flight to a private airstrip. After leveling off at flight level 280, the flight crew checked the weather conditions at nearby airports. Based on the weather information that they had, the pilot planned for a visual approach to the runway.

As the airplane neared the destination, the pilot flew over the runway and entered a left downwind visual traffic pattern to check if any animals were on the runway and what the windsock on the airstrip indicated. The pilot stated that they did not see the windsock as they passed over the runway. The pilot reported that there were turbulence and wind gusts from the hills below and to the west.

When the airplane was over the runway about 50 ft above ground level (agl), the pilot reduced the engine power to idle. The pilot reported the airplane then encountered wind shear; the airspeed dropped rapidly, and the airplane was "forced down" to the runway. A representative at the airstrip reported that the airplane hit hard on landing. The pilot unlocked the thrust reversers, applied brakes, and reached to deploy the ground spoilers. As he deployed the thrust reversers, the pilot said it felt like the right landing gear collapsed. He applied full left rudder and aileron, but the airplane continued to veer to the right. The pilot tried using the tiller to steer to the left but got no response. The airplane left the side of the runway and went into the grass, which resulted in substantial damage; the right main landing gear was broken aft and collapsed under the right wing.

Postaccident examinations of the airplane revealed no preimpact mechanical malfunctions or failures that would have precluded normal operation.

A review of weather conditions showed surface winds out of the north to northwest at 15 kts, with some gusts up to 20 kts. There was potential for turbulence and wind shear below 5,000 ft, but there were no direct observations. The area forecast about 30 minutes after the accident called for northwesterly winds at 10 to 17 kts with a few higher gusts in the afternoon for the general area.

Data from an onboard enhanced ground proximity warning system (EGPWS) revealed that the crew received a terrain alert just before the airplane crossed the runway threshold. At the time the airplane was over the runway threshold, it was 48 ft agl and in a 1,391 ft per minute rate of descent. The airplane impacted the runway 3 seconds later.

Given the pilot's account, the weather information for the area, and the data from the airplane's EGPWS, it is likely that the airplane encountered wind shear while transitioning from approach to landing.

Probable cause

The airplane’s encounter with wind shear on short final approach to the runway, which resulted in a hard landing and fracture of the right main landing gear.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN19LA054
Event ID
20190112X63300
Case number
CEN19LA054
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, coordinates. 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: 95e2107fe606b33a391dc695a2b1919c5b0843e13595c4a308ee47e4ff10abf1; retrieved 2026-09-16T08:32:33.354Z.