LAX07CA226 · Beech C23
Beech C23 · Accident: hard landing
From Taylor Airport (TYL) to an unrecorded destination
Event
- NTSB case
- LAX07CA226
- 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
Beech C23
- Aircraft type
- Beechcraft 23
- 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
- N6005X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Taylor Airport (TYL), Taylor, AZTo 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 · 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
- Destroyed
Cause areas
- Pilot in command › Directional control, not maintained
- Pilot in command › Flare, misjudged
- Pilot in command › Ground loop/swerve, not corrected
- Pilot in command › Porpoise/pilot-induced oscillation, encountered
- Pilot in command › Recovery from bounced landing, 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 student pilot flared too high, the airplane landed hard, and bounced down the runway in a porpoise before it veered off the runway into brush, caught fire, and was consumed in the post impact fire. The student had flown with his certified flight instructor (CFI) for about 50 minutes before he was signed off to complete a solo flight. The accident occurred on his first landing. While in the pattern, the student pilot attempted to avoid rain and shortened his downwind leg. After turning onto the base leg he discovered that he had turned too soon. He decided to continue the landing at a steeper than normal approach angle and a higher airspeed. He said he misjudged the flare and the airplane landed hard and bounced into the air. It then porpoised down the runway as it veered off to the left into the brush on the side of the runway. Both main landing gear were sheared off during the accident sequence.
Probable cause
the student pilot's misjudged landing flare and inadequate recovery from a bounced landing that resulted in a hard landing and a loss of directional control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX07CA226
- Event ID
- 20070829X01269
- Case number
- LAX07CA226
- 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: 3b2c2670865e0d5b2339a2855e7688aa785432cc1a5157c902d71b57314d342b; retrieved 2026-09-22T03:37:37.969Z.