- Date
- September 16, 1969
- Place
- San Francisco, CA · SAN FRANCISCO, CA
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Initial climb
- Aircraft
- N4137RPiper PA-32
- Status
- Completed · report March 13, 1970
- Report
- Brief approved by the director
- Safety recommendations
- Yes
- Case key
- 80072
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-3298 69/9/16 SAN FRANCISCO,CAL PIPER PA-32 CR- 0 0 1 COMMERCIAL COMMERCIAL, AGE 27, 2388 TIME - 1943 N4137R PX- 0 0 0 COMMUTER AIR CARRIER TOTAL HOURS, 444 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 AIR TAXI-CARGO S-D INSTRUMENT RATED. NAME OF AIRPORT - SAN FRANCISCO INT DEPARTURE POINT INTENDED DESTINATION SAN FRANCISCO,CAL SACRAMENTO,CALIF TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION TAKEOFF: INITIAL CLIMB COLLISION WITH GROUND/WATER: CONTROLLED LANDING: OTHER PROBABLE CAUSE(S) POWERPLANT - FUEL SYSTEM: SELECTOR VALVES MISCELLANEOUS ACTS,CONDITIONS - MATERIAL FAILURE MISCELLANEOUS ACTS,CONDITIONS - FUEL STARVATION COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING ON AIRPORT/SEAPLANE BASE/HELIPT. FIRE AFTER IMPACT REMARKS- FUEL SELECTOR VALVE MALFUNCTIONED. PLT CRASH LANDED ON APT TO AVOID HAZARDS BEYOND OVERRUN.
Aircraft
- Registration
- N4137R
- Reported as
- Piper PA-32
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- San Francisco Int
N4137RRegistered now · Piper PA-32-300Airframe modelPiper PA-32-300Engine modelLycoming TI0-540 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.