FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Miller Flying Servic Aero Commander 500-B accident

13 Jul 1987 · Mason City, IA, United States

Aero Commander 500-B · Accident: loss of control in flight during initial climb

From an unrecorded airport to Des Moines International Airport (DSM)

Report a problem

Event

NTSB case
MKC87FA138
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
0 · 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
Charter & commuter
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

Aero Commander 500-B

Aircraft type
Aero Commander 500
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
N9391R
Onboard fatalities
Unknown
Route
From not recordedTo Des Moines International Airport (DSM), Des Moines, IA
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 135: Air Taxi & Commuter
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
Initial climb
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

  • Fuselage, seat › Unlocked
  • Pilot in command › Checklist, not followed

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

NTSB narrative

THE AIRPLANE WAS IN A NORMAL APPEARING CLIMB AFTER TAKEOFF WHEN IT PITCHED UP TO A 70 TO 80 DEGREE ATTITUDE, STALLED, DROPPED THE RIGHT WING, THEN LEVELED THE WINGS AND HIT THE GROUND IN A NEAR-FLAT ATTITUDE. THE WEIGHT AND CG WERE WITHIN LIMITS. NO PREIMPACT PROBLEMS WERE FOUND THAT COULD CAUSE AN INADVERTENT PITCHUP. PILOT'S ONLY MEMORY IS THAT HE COULDN'T GET THE CONTROL COLUMN FAR ENOUGH FORWARD TO STOP THE PITCHUP. THE PILOT'S SEAT WAS FOUND IN THE FULL FORWARD POSITION WITH THE RIGHT LOCKING PIN IN THE LOCKING HOLE AND THE LEFT PIN 1/4TH OF AN INCH FORWARD OF THE FRONT LOCKING HOLE. THERE WERE NO VISIBLE MARKS ON EITHER OF THE LOCKING PINS. DEEP SCRATCHES WERE FOUND ON THE SIDES OF THE RAIL WHERE THE SEAT ATTACHMENTS NORMALLY SLIDE BACK AND FORTH WHEN THE SEAT IS ADJUSTED. EXAM OF THE OUTBOARD SIDE RECESSED SURFACE NEAR THE AFT END DISCLOSED WHAT APPEARED TO BE A FRESH SCRATCH.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record MKC87FA138
Event ID
20001213X31600
Case number
MKC87FA138
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1987-07-14.
  • API snapshot SHA-256: 2c19719cbdf99eafaef1d7c07ce427782ea2864c0a684ef2f080640711aa8feb; retrieved 2026-09-18T19:39:30.918Z.