FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA91FA171 · Beech 77

26 Jun 1991 · Magnolia, MS, United States

Beech 77 · Accident: in flight collision with object while maneuvering

From McComb-Pike County Airport / John E Lewis Field (MCB) to an unrecorded destination

Report a problem

Event

NTSB case
MIA91FA171
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
0
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

Beech 77

Aircraft type
Beechcraft 77
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
N60195
Operator
Roy Stewart
Onboard fatalities
Unknown
Route
From McComb-Pike County Airport / John E Lewis Field (MCB), McComb, MSTo not recorded
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
Maneuvering
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 collision with object
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(cfi) › Supervision, improper
  • Proper altitude › Not maintained

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

NTSB narrative

THE INSTRUCTOR PILOT (CFI) AND STUDENT WERE ON AN INSTRUCTIONAL FLIGHT IN VFR CONDITIONS. A WITNESS SAW AND HEARD THE AIRPLANE FLYING EASTBOUND. SHORTY THEREAFTER, THE AIRPLANE CRASHED ON A SOUTHERLY HEADING. THERE WAS EVIDENCE THAT INITIAL IMPACT OCCURRED, WHEN THE RIGHT WING TIP COLLIDED WITH TREETOPS. THE AIRPLANE REMAINED AIRBORNE FOR A DISTANCE, THEN CRASHED IN A STEEP DESCENT AFTER TRAVELING ABOUT 330 FT FROM WHERE THE FIRST PIECE OF THE WING TIP WAS FOUND. NO PREIMPACT PART FAILURE OR MALFUNCTION OF THE AIRCRAFT OR ENGINE WAS FOUND.

Probable cause

THE INSTRUCTOR PILOT'S (CFI'S) IMPROPER SUPERVISION OF FLIGHT AND A FAILURE TO MAINTAIN SUFFICIENT ALTITUDE ABOVE THE TREES.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA91FA171
Event ID
20001212X17335
Case number
MIA91FA171
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. 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: 1cb4aeb9289d56a1eef672b47a0f7d0d95a3de1370392a0f9af6c60145cb50be; retrieved 2026-09-21T01:44:49.791Z.