DFW05CA050 · Reinhart GP-4
Reinhart GP-4 · Accident: loss of control on ground/water during landing
From Bourland Field (50F) to an unrecorded destination
Event
- NTSB case
- DFW05CA050
- 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
Reinhart GP-4
- Aircraft type
- Reinhart GP-4
- 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
- N233CR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bourland Field (50F), Fort Worth, TXTo not recorded
- Aircraft age
- Not recorded
- 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 · landing roll
- First occurrenceThe 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
- Loss of control on ground/water
- 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
- Pilot in command › Compensation for wind conditions, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The 742-hour private pilot reported that during his departure from runway 17, the wind was from approximately 200 degrees at 10 knots. When he returned about an hour later, the wind had shifted to approximately 250-260 degrees at 15-20 knots with gusts. The pilot made two attempts at a crosswind landing on runway 17, each time striking a runway light with the airplane and initiating a go-around. The pilot reported that the right flap was damaged during the first attempt, and the landing gear retract link was damaged during the second landing attempt. During the third landing attempt, the pilot "used a forward slip technique to land, then kicked the nose around, and made what appeared to be a good landing." The left main landing gear then collapsed. The pilot reported that he held "hard right aileron to keep the left wing up as the airplane slid off to the left side of the runway." The airplane continued down into a ravine, and the propeller dug into the ground as the airplane made a 180-degree turn and came to rest upright.
Probable cause
The pilot's failure to compensate for the prevailing crosswind. A contributing factor was the crosswind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW05CA050
- Event ID
- 20050201X00126
- Case number
- DFW05CA050
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 85847d4a5a4b83d3c7fbf96fd69e2fceb62555814c49efa003842857ca2df238; retrieved 2026-09-22T06:22:23.221Z.