FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA11FA038 · Cessna 210A

28 Oct 2010 · Aiken, SC, United States

FBN of Catawba Cessna 210A · Accident: VFR encounter with IMC en route

From Beaufort Executive Airport (ARW) to Aiken Regional Airport (AIK)

Report a problem

Event

NTSB case
ERA11FA038
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
1 · all aircraft and ground
Ground fatalities
Unknown
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
Instrument Meteorological Cond

Cessna 210A

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
N6655X
Onboard fatalities
Unknown
Route
From Beaufort Executive Airport (ARW), Beaufort, SCTo Aiken Regional Airport (AIK), Aiken, SC
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
Defining eventThe 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
VFR encounter with IMC
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Psychological
  • Personnel issues › Task performance

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

NTSB narrative

During a visual flight rules (VFR) cross-country flight, an air traffic controller advised the non-instrument rated pilot that a broken line of weather with moderate-to-heavy precipitation existed, which extended almost to his destination airport. During the ensuing conversation, the pilot advised the controller that he was underneath the weather and that he had weather radar. The pilot then entered the weather in the vicinity of his destination airport. Radar imagery, witness statements, and measurements from local surface stations indicated that areas of light, moderate, and possibly heavy precipitation existed and that the airplane was most likely in instrument meteorological conditions in its final 2 minutes of flight. Review of radar data revealed that, after entering the weather, the pilot's altitude control became erratic, and the airplane entered an ever-tightening right turn, consistent with the pilot experiencing spatial disorientation. The airplane completed about two and a half 360-degree turns of progressively smaller diameter before radar contact was lost, and the airplane impacted terrain. No record of the pilot obtaining a weather briefing or filing a flight plan was discovered.

Examination of the wreckage revealed no evidence of any preimpact malfunction or failure of the airplane or engine, and it did not reveal any evidence that on-board weather radar was installed. During the wreckage examination, the remains of a portable global positioning system receiver were discovered. The receiver was not certificated for use under instrument flight rules and was intended by the manufacturer to be used as an aid for VFR navigation. It was capable of displaying weather data and images from the NEXt-generation RADar (NEXRAD) ground radar network, but, unlike on-board weather radar, transmitted NEXRAD data is not real-time. The receiver manufacturer cautioned that the lapsed time between collection, processing, and dissemination of NEXRAD images can be significant, and, therefore, they should only be used for long-range planning purposes and not for short-range weather avoidance.

Furthermore, according to the Federal Aviation Administration (FAA), NEXRAD data or any radar data should not be used to penetrate hazardous weather. Rather, it should be used in an early-warning capacity of pre-departure and en route evaluation. As discussed in the Safety Alert issued by the National Transportation Safety Board (NTSB) on in-cockpit NEXRAD, because NEXRAD images present radar data from multiple ground sites as a single mosaic image, the age indicated on the NEXRAD image does not show the age of the actual weather conditions but rather represents the time when the mosaic image was created. The actual weather conditions could be up to 15 to 20 minutes older than the age indicated on the image. Both the FAA and the NTSB advise that advanced avionics weather data systems should not be used as a substitute for a pre-flight weather briefing.

Probable cause

The pilot's inadequate weather planning and improper decision to continue a visual flight rules flight into instrument meteorological conditions, which resulted in a loss of control due to spatial disorientation. Contributing to the accident was the pilot’s improper use of in-cockpit next generation radar imagery for short-range weather avoidance.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA11FA038
Event ID
20101028X12506
Case number
ERA11FA038
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 4c0badec7d9625d1c59a240b6b7cf619b33ecea40840a4eb1fa9241abe29542a; retrieved 2026-09-13T21:06:48.218Z.