- Date
- December 3, 1972
- Place
- Baytown, TX · BAYTOWN, TX
- Injuries
- 3 fatal, 1 serious
- Damage
- Destroyed
- Phase of flight
- Approach
- Aircraft
- N3782WPiper PA-32
- Status
- Completed · report March 28, 1973
- Report
- Brief approved by the director
- Case key
- 169323
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-3743 72/12/3 BAYTOWN,TEX PIPER PA-32 CR- 1 0 0 NONCOMMERCIAL PRIVATE, AGE 35, 440 TIME - 1824 N3782W PX- 2 1 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 334 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - HUMPHREY DEPARTURE POINT INTENDED DESTINATION SEGUIN,TEX BAYTOWN,TEX TYPE OF ACCIDENT PHASE OF OPERATION COLLISION WITH GROUND/WATER: CONTROLLED LANDING: TRAFFIC PATTERN-CIRCLING PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS FACTOR(S) PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING WEATHER - LOW CEILING WEATHER - FOG WEATHER BRIEFING - NO RECORD OF BRIEFING RECEIVED WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE OBSCURATION 0 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 1/4 MILE OR LESS NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE WIND DIRECTION-DEGREES FOG 130 WIND VELOCITY-KNOTS TYPE OF WEATHER CONDITIONS 5 IFR TYPE OF FLIGHT PLAN NONE REMARKS- DESCENDED INTO GRND IN FOG TRYING TO LND.
Aircraft
- Registration
- N3782W
- Reported as
- Piper PA-32
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Humphrey
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.