FTW88LA098 · Cessna 170
Cessna 170 · Accident: in flight encounter with weather en route
From David Wayne Hooks Memorial Airport (DWH) to Beaumont Municipal Airport (BMT)
Event
- NTSB case
- FTW88LA098
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Unknown
Cessna 170
- Aircraft type
- Cessna 170
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N3853V
- Operator
- Robinson, Richard L. · private individual
- Onboard fatalities
- Unknown
- Route
- From David Wayne Hooks Memorial Airport (DWH), Tomball, TXTo Beaumont Municipal Airport (BMT), Beaumont, TX
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · cruise
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- In flight encounter with weather
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Flight into known adverse weather, performed
- Pilot in command › Proper altitude, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT STRUCK TREES AND THE GRND DURING A NIGHT CROSS COUNTRY IN MARGINAL WEATHER. THE NON-INSTRUMENT RATED PVT PLT STATED THAT HE WAS FLYING IN CRUISE FLT AT 1250' MSL WHEN HE HIT TREES. THE CLOSEST WX STATION RECORDED 1200 OVERCAST WITH 5 MILES VISIBILITY, TEMP 74, DEW PT 70. THE AREA OF THE ACCIDENT SITE WAS SPARSELY POPULATED AND KNOWN TO DEVELOP FOG AND RAGGED CEILINGS DURING SIMILAR CONDITIONS. THE ACDT SITE ELV WAS 15' AND THE TREES WERE 60-100' TALL. PLT RPTD THAT HIS ALTIMETER MALFUNCTIONED, HOWEVER, POST-ACCIDENT EXAMINATION AND TESTING DID NO REVEAL ANY FAILURE OR MALFUNCTION IN THE LOWER ALTITUDES. ALTIMETER WAS LAST CALIBRATED AND TESTED 17 YRS PRIOR TO THE ACCIDENT. THE SURVIVORS WERE LOCATED ABOUT 16 HRS AFTER THE ACCIDENT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record FTW88LA098
- Event ID
- 20001213X25696
- Case number
- FTW88LA098
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1988-05-09.
- API snapshot SHA-256: d3ad023bba0aefe9594b8d950afb53dd3574ca37bd87c3040718e39aea59b85a; retrieved 2026-09-21T16:10:59.227Z.