- Date
- August 4, 1965
- Place
- Union Bridge, MD · UNION BRIDGE, MD
- Injuries
- 2 fatal
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N4778PPiper PA-23
- Status
- Completed · report January 27, 1966
- Report
- Brief approved by the director
- Case key
- 176748
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-1112 65/8/4 UNION BRIDGE MD PIPER PA-23 CR- 1 0 0 NONCOMMERCIAL PRIVATE, AGE 39, 565 TIME - 1945 N4778P PX- 1 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 360 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. TYPE OF ACCIDENT PHASE OF OPERATION LIGHTNING STRIKE IN FLIGHT: NORMAL CRUISE AIRFRAME FAILURE: IN FLIGHT IN FLIGHT: UNCONTROLLED DESCENT PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS WEATHER - LIGHTNING STRIKE WEATHER - THUNDERSTORM ACTIVITY FACTOR(S) AIRFRAME - FUSELAGE: WINDSHIELDS,WINDOWS,CANOPIES WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, BY PHONE WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE BROKEN 5000 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 5 OR OVER(UNLIMITED) RAIN, THUNDERSTORM TEMPERATURE-F WIND DIRECTION-DEGREES 74 140 WIND VELOCITY-KNOTS TYPE OF WEATHER CONDITIONS 8 IFR TYPE OF FLIGHT PLAN NONE FIRE AFTER IMPACT REMARKS- LIGHTNING STRIKE ON ACFT IMMEDIATLY BFOR CRASH,WAS WITNESSED BY GROUND OBSERVERS.
Aircraft
- Registration
- N4778P
- Reported as
- Piper PA-23
- 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.