FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

2006 Cessna 210A crash

19 Apr 2006 · Ludville, Georgia, U.S.

Cessna 210A · ATC error, Foul weather, Pilot error

From Prattville - Grouby Field (1A9) to Washington Manassas Harry P. Davis Field (HEF)

Report a problem

Event

NTSB case
CHI06MA115
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
Unknown
Event fatalities
1 · all aircraft and ground
Ground fatalities
Unknown
Occupants
Unknown
Survivors
Unknown
InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
0 serious · 0 minor (NTSB)
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
N6579X
Operator
Unknown
Onboard fatalities
Unknown
Route
From Prattville - Grouby Field (1A9), Prattville, ALTo Washington Manassas Harry P. Davis Field (HEF), Manassas, VA
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
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

  • Atc personnel(artcc) › In flight weather avoidance assistance, not performed
  • Pilot in command › Aircraft control, not possible

Approximate · Coordinates as the NTSB recorded them, without a stated acquisition method; they lie within 50 km of Ludville, GA, the place the record names, and are not otherwise checked.

From the Wikipedia article

Albert Scott Crossfield (October 2, 1921 – April 19, 2006) was an American naval officer and test pilot. In 1953, he became the first pilot to fly at twice the speed of sound. Crossfield was the first of twelve pilots who flew the North American X-15, an experimental spaceplane jointly operated by the United States Air Force and NASA. He is the subject of a biography called "Always Another Dawn."

Text from the Wikipedia article “Albert Scott Crossfield” (revision 1367616922, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article

NTSB narrative

The airplane flew into an area of severe thunderstorms identified as a mesoscale convective system (or "MCS") with intense to extreme intensities during cruise flight at 11,000 feet then descended rapidly and impacted the terrain. The on-scene investigation revealed no preimpact mechanical malfunctions or anomalies that would have prevented the normal operation of the airplane or its systems.

The airplane entered the severe convective weather; the pilot then requested and received clearance from the air traffic controller to initiate a turn to escape the weather. The airplane was lost from radar about 30 seconds after the pilot initiated the turn. Before the airplane entered the weather, the controller's radar scope depicted a band of moderate to extreme weather along the accident airplane's projected flightpath that was consistent with an embedded, heavy-precipitation, supercell-type thunderstorm; however, the controller did not provide the pilot with any severe weather advisories and did not advise the pilot of the weather depicted on his radar scope.

Although Federal Aviation Administration directives state that controllers should give first priority to separating aircraft and issuing safety alerts, the directives further state that controllers should use good judgment and first perform the action that is most critical from a safety standpoint. Review of air traffic communications and radar data identified no air traffic control (ATC) radar limitations, no excessive traffic, no radio frequency congestion, and no controller workload issues that would have prevented the controller from issuing pertinent weather information to the accident pilot. On the basis of the controller's workload and available resources, he should have recognized that the adverse weather represented an immediate safety hazard to the accident flight and should have provided appropriate advisories to the pilot.

The pilot obtained several weather briefings before departure. At that time, the current weather along the route of flight showed significant convective activity and a moving squall line, and the forecast predicted significant thunderstorm activity along the planned route of flight. The pilot also discussed the weather with an acquaintance, mentioning that he might need to work his way around some weather. On the basis of the weather information obtained by the pilot and his comments regarding the weather, the pilot was aware before departure that he would likely encounter adverse weather along the planned route of flight; however, by the time the airplane encountered the weather, the pilot had been airborne for over an hour and had not requested any updated weather information from air traffic controllers. The airplane was equipped with a BF Goodrich WX-950 Stormscope, which has some ability to depict the location and frequency of lightning strikes in the vicinity of the airplane; however, the investigation could not determine if and how this equipment may have been used during the flight. The airplane was not configured to display satellite weather information on its global positioning systems.

In October 2006, the National Transportation Safety Board issued Safety Alert SA-11, "Thunderstorm Encounters," as a result of this accident and three other fatal accidents that involved in-flight encounters with severe weather. The safety alert addresses ATC involvement in these accidents. The alert also states that IFR pilots need to actively maintain awareness of severe weather along their route of flight, and it provides suggestions to assist pilots in avoiding involvement in similar accidents. The safety alert can be found at the Safety Board's Web site at http://www.ntsb.gov/alerts/SA_011.pdf.

Probable cause

The pilot's failure to obtain updated en route weather information, which resulted in his continued instrument flight into a widespread area of severe convective activity, and the air traffic controller's failure to provide adverse weather avoidance assistance, as required by Federal Aviation Administration directives, both of which led to the airplane's encounter with a severe thunderstorm and subsequent loss of control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

Wikipedia article: Albert Scott Crossfield
Article
Albert Scott Crossfield
Revision
1367616922 · 2026-08-04 · retrieved 2026-09-18
Wikidata
Q955842
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record CHI06MA115
Event ID
20060501X00494
Case number
CHI06MA115
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Where each value comes from
Record
Wikipedia article "Albert Scott Crossfield" (page 748827, revision 1367616922); merged with NTSB case CHI06MA115 (events / aircraft)
Date
NTSB record CHI06MA115: events.ev_date
Place and country
Wikipedia infobox: site; country from NTSB record CHI06MA115
Map position
NTSB record CHI06MA115: events decimal coordinates (no acquisition method recorded), within 50 km of the named town (GeoNames)
Aircraft, operator and route
NTSB record CHI06MA115: aircraft; gaps from Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
Operation
NTSB record CHI06MA115: operated under Part 91: General Aviation
Fatalities
Wikipedia: Wikipedia infobox: aircraft fatalities (the NTSB record states no total)
Ground fatalities
NTSB record CHI06MA115: events.inj_f_grnd
Summary
Wikipedia infobox: summary
Source notes (2)
  • One occurrence in two sources, merged: the Wikipedia article "Albert Scott Crossfield" and NTSB case CHI06MA115, matched by the same aircraft registration and date. For this US event the NTSB's values are used where the two differ; each value names its source.
  • The date is the UTC date the NTSB stores; the local date may be a day earlier.