- Date
- June 15, 1972
- Place
- Columbia, NJ · COLUMBIA, NJ
- Injuries
- 2 fatal
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N30025Cessna 177A
- Status
- Completed · report December 12, 1972
- Report
- Brief approved by the director
- Case key
- 166590
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-0911 72/6/15 COLUMBIA,NJ CESSNA 177A CR- 1 0 0 NONCOMMERCIAL COMMERCIAL, AGE 38, 350 TIME - 0605 N30025 PX- 1 0 0 BUSINESS TOTAL HOURS, UNK/NR IN DAMAGE-DESTROYED OT- 0 0 0 TYPE, INSTRUMENT RATED. NAME OF AIRPORT - BLAIRSTOWN DEPARTURE POINT INTENDED DESTINATION CALDWELL,NJ BLAIRSTOWN,NJ TYPE OF ACCIDENT PHASE OF OPERATION COLLISION WITH GROUND/WATER: CONTROLLED IN FLIGHT: NORMAL CRUISE PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS FACTOR(S) WEATHER - LOW CEILING WEATHER - RAIN WEATHER - FOG PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING WEATHER BRIEFING - NO RECORD OF BRIEFING RECEIVED WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT MISSING AIRCRAFT - LATER RECOVERED SKY CONDITION CEILING AT ACCIDENT SITE OBSCURATION 0 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 1/4 MILE OR LESS RAIN OBSTRUCTIONS TO VISION AT ACCIDENT SITE TYPE OF WEATHER CONDITIONS FOG VFR TYPE OF FLIGHT PLAN NONE REMARKS- FLEW INTO OBSCURED MTN. RECOVERY DATE 6/19/72.
Aircraft
- Registration
- N30025
- Reported as
- Cessna 177A
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Blairstown
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.