LAX94LA082 · Cessna 175
Cessna 175 · Accident: in flight collision with object during initial climb
Event
- NTSB case
- LAX94LA082
- 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
- 2 · all aircraft and ground
- Ground fatalities
- 0
- 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
Cessna 175
- Aircraft type
- Cessna 175
- 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
- N6623E
- Operator
- Hoyt A. Phelps · private individual
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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
- Initial climb
- 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
- In flight collision with object
- 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 › Altitude, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Witnesses reported observing the pilot taxi onto the 2,000-foot long runway from an intersection which afforded him between 1,200 and 1,400 feet of usable runway. Nothing unusual was noted during the airplane's ground roll and lift-off, and the airplane began climbing. After the airplane gained between 30 and 60 feet, its pitch attitude lowered, and no additional altitude was gained. The airplane's landing gear collided with a perimeter chainlink fence and cactus, and the airplane came to rest about 1\4 mile from the airstrip. The airplane was recovered from the accident site and was examined. No mechanical discrepancies were found with any airplane system or with the engine.
Probable cause
the pilot's failure to attain sufficient altitude following takeoff. A factor in the accident was the pilot's failure to use all available runway for takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX94LA082
- Event ID
- 20001211X13884
- Case number
- LAX94LA082
- 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. 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: a54348bd347d1f998ba632db1ed2369d02a0f1ba98ccd4d3529245ef19bb035d; retrieved 2026-09-21T00:16:54.922Z.