SEA06CA093 · Zenair CH 2000
Zenair CH 2000 · Accident: hard landing
From Salt Lake City International Airport (SLC) to Bolinder Field Tooele Valley Airport (TVY)
Event
- NTSB case
- SEA06CA093
- 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
Zenair CH 2000
- Aircraft type
- Zenair 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
- N8503J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Salt Lake City International Airport (SLC), Salt Lake City, UTTo Bolinder Field Tooele Valley Airport (TVY), Tooele, UT
- 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
- 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
- Flare › Improper
- Pilot in command(cfi) › Supervision, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the flight instructor, the airplane touched down on the main landing gear and bounced. He added "power to help soften the landing," and at this point, the student "released his grip on the flight controls, causing the nose of the aircraft to pitch up dramatically. Almost immediately after the initial upward pitch, the aircraft dropped down hard on the nose wheel, which broke off." The airplane slid off the right side of the runway, the nose landing gear collapsed, and the airplane came to a stop nose down. An FAA inspector examined the airplane and reported that the firewall was damaged.
Probable cause
The flight instructor's inadequate supervision of the student pilot during the landing flare, which resulted in a hard landing. A contributing factor was the student pilot's failure to maintain aircraft control during the landing flare.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA06CA093
- Event ID
- 20060525X00637
- Case number
- SEA06CA093
- 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: 69e83878971711142189ca565f9819c1d0cbe7fc48072efe05b124e20599ce3d; retrieved 2026-09-22T04:58:32.644Z.