FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA07FA154 · North American Navion

21 Sept 2007 · Clayton, NC, United States

North American Navion · Accident: in flight encounter with weather en route

From Conway Horry County Airport (HYW) to Culpeper Regional Airport (CJR)

Report a problem

Event

NTSB case
MIA07FA154
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

North American Navion

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
N8844H
Operator
Unknown
Onboard fatalities
Unknown
Route
From Conway Horry County Airport (HYW), Conway, SCTo Culpeper Regional Airport (CJR), Culpeper, 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

  • Pilot in command › Maneuver to avoid obstructions, intentional

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

NTSB narrative

The instrument rated pilot who had not logged any actual instrument flight time did not obtain any preflight weather briefing with either Lockheed Martin FSS or DUATS. Instrument meteorological conditions (IMC) due to low ceilings and visibility were forecast to exist between the departure airport and the crash site location, though VFR conditions existed at the destination airport at both the departure time and estimated time of arrival. The flight departed under VFR, and proceeded in a northeasterly direction to a point approximately 59 nautical miles north-northeast from the departure airport where it was identified on radar. The flight was observed on radar for 55 nautical miles, and never flew higher than 800 feet pressure altitude. The flight continued in a northeasterly direction gradually descending while the terrain elevation gradually increased. A ceiling of broken clouds at 400 feet above ground level (agl) was noted at an airport 21 nautical miles from the crash site. For the last 9 minutes 31 seconds of the flight, the ground speed never decreased less than 110 knots. The airplane descended to 265 feet agl, and at the last radar return, which was located 0.18 nautical miles from the crash site, the ground speed was 130 knots. While approaching an antenna tower and water tower which were ahead of the flight path and 215 and 185 feet agl, respectively, the pilot banked hard to the right, and with the engine operating at approximately 2,300 rpm, the airplane impacted the parking lot of a restaurant. The airplane crashed into the restaurant, and was fragmented. A fire erupted at impact and the restaurant sustained impact and fire damage. Examination of the airframe, flight controls, engine, engine accessories, and propeller revealed no evidence of preimpact failure or malfunction.

Probable cause

The pilot's intentional abrupt maneuver during low altitude cruise flight to avoid obstructions ahead, resulting in an in-flight collision with terrain and a building. Contributing to the accident were the failure of the pilot to obtain a preflight weather briefing and his flight into known IMC.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA07FA154
Event ID
20070925X01444
Case number
MIA07FA154
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: 210ab8a951edda488941de9d9d9fc954ddf49759be6c4594db36bd7184c05890; retrieved 2026-09-20T16:15:59.349Z.