- Date
- November 13, 1969
- Place
- Princeton, NJ · PRINCETON, NJ
- Injuries
- 1 minor
- Damage
- Destroyed
- Phase of flight
- Approach
- Aircraft
- N7349VBellanca 17-30
- Status
- Completed · report January 18, 1970
- Report
- Brief approved by the director
- Case key
- 180870
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-2782 69/11/13 PRINCETON,NJ BELLANCA 17-30 CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 36, 500 TIME - 1410 N7349V PX- 0 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 45 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - PRINCETON DEPARTURE POINT INTENDED DESTINATION LAST ENROUTE STOP WISCASSET,ME N PHILADELPHIA,PA SANFORD,ME TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION LANDING: FINAL APPROACH STALL: SPIN LANDING: FINAL APPROACH PROBABLE CAUSE(S) PILOT IN COMMAND - MISMANAGEMENT OF FUEL PILOT IN COMMAND - FAILED TO FOLLOW APPROVED PROCEDURES,DIRECTIVES,ETC. MISCELLANEOUS ACTS,CONDITIONS - FUEL STARVATION PILOT IN COMMAND - IMPROPER OPERATION OF FLIGHT CONTROLS PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED PARTIAL POWER LOSS - PARTIAL LOSS OF POWER - 1 ENGINE EMERGENCY CIRCUMSTANCES - PRECAUTIONARY LANDING ON AIRPORT LOW ON FUEL FIRE AFTER IMPACT REMARKS- FUEL EXHAUSTED,CHGD TNK,ENG SURGED.ACFT OBSVD NOSE HIGH PITCH DWN HIT BLDG.BOTH DESTROYED BY FIRE.
Aircraft
- Registration
- N7349V
- Reported as
- Bellanca 17-30
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Princeton
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.