- Date
- March 19, 1966
- Place
- Lake Charles, LA · LAKE CHARLES, LA
- Injuries
- 2 fatal
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N7355YPiper PA-30
- Status
- Completed · report October 6, 1966
- Report
- Brief approved by the director
- Case key
- 174173
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 ---------------------------------------------------------------------------------------------------------------------------- 2-0251 66/3/19 LAKE CHARLES LA PIPER PA-30 CR- 1 0 0 MISCELLANEOUS COMMERCIAL, AGE 47, 17500 TIME - 0640 N7355Y PX- 1 0 0 OTHER PUBLIC TOTAL HOURS, 1000 IN DAMAGE-DESTROYED OT- 0 0 0 TYPE, INSTRUMENT RATED. 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 PILOT IN COMMAND - SPATIAL DISORIENTATION TERRAIN - GLASSY WATER FACTOR(S) WEATHER - LOW CEILING WEATHER - FOG MISCELLANEOUS ACTS,CONDITIONS - AIRCRAFT CAME TO REST IN WATER WEATHER BRIEFING - NO RECORD OF BRIEFING RECEIVED WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE OVERCAST 800 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 1/4 MILE OR LESS NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE TEMPERATURE-F FOG 63 WIND DIRECTION-DEGREES WIND VELOCITY-KNOTS 210 5 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN IFR SPECIAL VFR REMARKS- PILOT ADVISED LAKE CHARLES CONTROL CONDITIONS WERE IFR AT THE DEPARTURE AIRPORT
Aircraft
- Registration
- N7355Y
- Reported as
- Piper PA-30
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
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.