- Date
- July 23, 1970
- Place
- Chula Vista, CA · CHULA VISTA, CA
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Initial climb
- Aircraft
- N7275JPiper PA-28
- Status
- Completed · report April 27, 1971
- Report
- Brief approved by the director
- Case key
- 114332
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
NTSB brief
NTSB’s brief of the accident, as it was printed: the coded facts, with the probable cause and factors.
---------------------------------------------------------------------------------------------------------------------------- FILE DATE LOCATION AIRCRAFT DATA INJURIES FLIGHT PILOT DATA F S M/N PURPOSE ---------------------------------------------------------------------------------------------------------------------------- 3-2863 70/7/23 CHULA VISTA,CALIF PIPER PA-28 CR- 0 0 1 INSTRUCTIONAL STUDENT, AGE 25, 134 TIME - 1120 N7275J PX- 0 0 0 SOLO TOTAL HOURS, 23 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - BROWN FIELD DEPARTURE POINT INTENDED DESTINATION CHULA VISTA,CALIF LOCAL TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION TAKEOFF: INITIAL CLIMB COLLIDED WITH: OBJECT LANDING: ROLL PROBABLE CAUSE(S) PERSONNEL - MAINTENANCE,SERVICING,INSPECTION: INADEQUATE INSPECTION OF AIRCRAFT (MAINTENANCE PERSONNEL) POWERPLANT - ENGINE CONTROLS: THROTTLE-POWER LEVER ASSEMBLIES MISCELLANEOUS ACTS,CONDITIONS - LOOSE,PART/FITTING PARTIAL POWER LOSS - PARTIAL LOSS OF POWER - 1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND REMARKS- 29.6HR SINCE 100HR INSP.THROTTLE ARM ON CARB LOOSE.LYCOMING BULLETIN 330 CVRS.L WING HIT WASHTUB.
Aircraft
- Registration
- N7275J
- Reported as
- Piper PA-28
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Brown Field
N7275JRegistered now · Piper PA-28-140Airframe modelPiper PA-28-140Engine modelLycoming 0-320 series
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.