FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL07FA010 · Cessna 182T

22 Oct 2006 · Rocky Mount, NC, United States

Cessna 182T · Accident: loss of control in flight en route

From Michael J. Smith Field (MRH) to Rocky Mount Wilson Regional Airport (RWI)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ATL07FA010
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
2 · 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 182T

Aircraft type
Cessna 182
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
N2135L
Onboard fatalities
Unknown
Route Possible conflict
From Michael J. Smith Field (MRH), Beaufort, NCTo Rocky Mount Wilson Regional Airport (RWI), Rocky Mount, NC
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
Loss of control in flight
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

  • Pilot in command › Aircraft control, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot had filed an IFR flight to Wilson Industrial Air Center Airport, Wilson, North Carolina (W03). A review of radar data showed the flight overflew W03 then diverted to Rocky Mount-Wilson Regional Airport (RWI), Rocky Mount, North Carolina. An airport employee at RWI stated that, while towing a King Air out of a hangar, he heard a pilot announce over the radio that he was making an approach to runway 4. He stated that the weather at the time was light rain, fog, and mist, and that winds were light and favoring runway 4. He said that he could not see the airplane on approach until it broke through the clouds, approximately 600 to 700 feet above ground level (AGL) estimated, and it was well left of the runway centerline. He could see that it was a Cessna 182. The airplane then climbed back into the clouds and departed the area to the northwest. The next radio communication the employee heard was a King Air pilot asking it anyone was talking to the Cessna 182, as Washington Center had lost contact. Recorded audio communication between the pilot and Washington Air Route Traffic Control Center (ARTCC) found that the pilot reported to ARTCC that he was doing a missed approach at RWI. The controller told the pilot to climb and maintain 3,000 feet. The pilot then requested an alternate destination and the controller listed several airports including Greenville, North Carolina. The pilot asked about the weather at Greenville and the controller reported that the weather was; visibility 7 miles, scattered clouds at 600 feet, broken clouds at 3200 feet, and overcast ceiling at 5500 feet. The pilot accepted the alternate of Greenville and the controller told the pilot to climb and maintain 3,000 feet and turn right direct Greenville. Several seconds passed and the controller asked the pilot "did you copy", the pilot stated "copied yes mam". This was the last radio transmission received from the pilot. The airplane impacted the ground in a steep nose down attitude leaving a 4-foot deep crater. Examination of the airplane found no preimpact mechanical failure or malfunctions that would have prevented the airplane from operating properly. According to the pilot's logbook he had accumulated about 271 hours total time as of September 22, 2006, and 3.3 hours of actual instrument time in the last 90 days preceding the accident.

Probable cause

The pilot's failure to maintain aircraft control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL07FA010
Event ID
20061026X01559
Case number
ATL07FA010
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, coordinates. 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: 7236dfddfc88d7848dd12dcc58e578db352bca271359b83708cfa7698ce7c521; retrieved 2026-09-20T17:01:14.520Z.