FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW83FA031 · Cessna P210N

2 Nov 1982 · Normangee, TX, United States

Roloff Evangelistic Enterprise Cessna P210N · Accident: in flight encounter with weather en route

From C · Corpus Christi, TX to C · Kansas City, MO

Report a problem

Event

NTSB case
FTW83FA031
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
4 · 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
Visual Meteorological Cond

Cessna P210N

Aircraft type
Cessna 210
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
N612J
Onboard fatalities
Unknown
Route
From C · Corpus Christi, TXTo C · Kansas City, MO
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 · climb to 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
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 › Design stress limits of aircraft, exceeded
  • Pilot in command › Flight controls, improper use of
  • Pilot in command › Flight into known adverse weather, continued

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

A COMPANY PLT RECEIVED TWO WX BRIEFINGS FROM THE SAN ANTONIO FSS, ONE WAS AT ABOUT 1700 THE DAY BEFORE THE ACCIDENT & THE OTHER ON 11/2. AFTER EACH WX BRIEFING THE COMPANY PLT BRIEFED THE PLT OF THE ACCIDENT ACFT. THE ACFT DEPARTED AT ABOUT 0835. AT 0953 THE PLT CONTACTED FLIGHT WATCH & WAS ADVISED OF A CONVECTIVE SIGMET OF EMBEDDED THUNDERSTORMS. AT 1001 THE PLT REQUESTED & WAS CLEARED TO FL190. THIS WAS THE LAST RADIO CONTACT WITH THE ACFT. IN FLIGHT SEPARATION OF THE WINGS, VERTICAL & HORIZONTAL STABILIZERS OCCURRED. THE ACFT PENETRATED A DENSE AREA OF THUNDERSTORMS WITH ACTIVITY UP TO INTENSE (LEVEL 5) & PROBABLY ENCOUNTERED SEVERE TURBULENCE. IN ADDITION THERE WOULD PROBABLY BEEN MODERATE TO SEVERE ICING IN RAIN SHAFTS WITHIN THE THUNDERSTORMS AT THE ACFT'S FLIGHT ALTITUDE. THE 0817 WX BRIEFING WAS INADEQUATE IN THAT THE AREA FORECAST WHICH WARNED OF THUNDERSTORM ACTIVITY ENROUTE WAS NOT UTILIZED.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record FTW83FA031
Event ID
20020917X04640
Case number
FTW83FA031
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: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 168431cee4e967eb447130ab14a689e0a186fd6b8776092e4102f3ccc6db2dd1; retrieved 2026-09-21T07:34:35.023Z.