DFW05CA108 · Aircraft Mfg & Dev. Co. (AMD) CH-2000
Coyote Aviation Aircraft Mfg & Dev. Co. (AMD) CH-2000 · Accident: loss of control on ground/water during landing
From Rick Husband Amarillo International Airport (AMA) to Rick Husband Amarillo International Airport (AMA)
Event
- NTSB case
- DFW05CA108
- 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
Aircraft Mfg & Dev. Co. (AMD) CH-2000
- Aircraft type
- Aircraft MFG Dev Co (amd) CH-2000
- 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
- N215LF
- Operator
- Coyote Aviation
- Onboard fatalities
- Unknown
- Route
- From Rick Husband Amarillo International Airport (AMA), Amarillo, TXTo Rick Husband Amarillo International Airport (AMA), Amarillo, TX
- 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 · flare/touchdown
- 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, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
A 639-hour flight instructor pilot and 15-hour student pilot flew to another airport to practice crosswind landings. According to the flight instructor, the wind was reported from 320 degrees at 15 knots, gusting to 25 knots, and runway 35 was in use. During the landing flare and with the student pilot at the controls, round out was started somewhat early (about 25 feet above the ground); the airplane dropped 2-3 feet onto the main landing gear. The aircraft bounced in to the air, and the flight instructor reported that the right rudder pedal left his foot rapidly, putting the right wing tip on to the runway.
Probable cause
The student pilot's improper compensation for existing wind conditions. Contributing factors were the crosswind and inadequate supervision by the flight instructor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW05CA108
- Event ID
- 20050510X00584
- Case number
- DFW05CA108
- 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: 8c13acb0efa0790bed76a90f03740c60fe1823bd7f05311a564b40fefb20f180; retrieved 2026-09-22T06:01:09.027Z.