FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA02FA170 · Beagle Aircraft B-206 Series 2

21 Sept 2002 · McAlpin, FL, United States

Beagle Aircraft B-206 Series 2 · Accident: loss of control in flight on approach

From 23J · Jacksonville, FL to McAlpin, FL

Report a problem

Event

NTSB case
MIA02FA170
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
Visual Meteorological Cond

Beagle Aircraft B-206 Series 2

Aircraft type
Beagle B-206
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
N86GW
Operator
Unknown
Onboard fatalities
Unknown
Route
From 23J · Jacksonville, FLTo McAlpin, FL
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
Approach · VFR pattern turn to base
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
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall
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 › Airspeed, not maintained
  • Pilot in command › Stall, inadvertent

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

NTSB narrative

The airplane impacted terrain in a nose low pitch attitude after the private pilot lost control during a turn from base to final approach. Witnesses located at the arrival airport reported the accident airplane flew a fairly "tight" right downwind pattern for runway 36 that was a "little low" (about 650 to 750 feet above ground level [agl]). The surface winds were from the east, and according to the witnesses, the result was that the pilot overshot his turn to final approach. The pilot corrected back toward the centerline in a fairly steep bank when the airplane was observed to enter a roll to the right, the nose dropped toward the ground. The witnesses then lost sight of the airplane as it descended behind trees in a nose low pitch attitude. Witnesses estimated the altitude of the airplane at the time of the roll was between 300 and 350 feet agl. The private pilot flew the airplane once within the preceding 6 months and twice within the past 12 months. No anomalies with the airframe or engines were noted that would have prevented their normal operation. According to the fixed-based operator, where the airplane was based, fueling personnel added 10 gallons to each wing prior to the accident flight; however, they were not sure what the airplane's total fuel quantity was. The unusable fuel quantity was 6.1 gallons. The fuel consumption rate varied between 24.4 and 33.0 gallons per hour depending on the power setting, and the accident flight lasted 35 minutes. No fuel was found in the fuel system components for the right engine with the exception of the fuel manifold. It was possible that the right engine's fuel supply line may have become unported during the steep bank to final; however, with an unknown fuel quantity, this could not be determined conclusively. Toxicology tests performed on the pilot were positive for tramadol (prescription painkiller) and chlorpheniramine (antihistamine, commonly used in over-the-counter cold/allergy preparations). Side effects for the drugs include dizziness, sleepiness, and performance degradation for complex cognitive and motor tasks. It is likely the use of the two drugs impaired the pilot's judgment and performance in pre-flight planning and in the flight itself.

Probable cause

the pilot's failure to maintain an adequate airspeed to sustain controlled flight, which resulted in an inadvertent stall during a turn from base to final. A contributing factor was the pilot's use of judgment and performance impairing drugs.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA02FA170
Event ID
20020926X05217
Case number
MIA02FA170
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: 1a7f692e19ff147197644e375f1f073b88cc028f8f4f2b4c4cf1dc43bdfec29f; retrieved 2026-09-20T19:47:30.832Z.