The U.S. aircraft register, updated daily
Accidents · NTSB CHI90DEM02 · Final report

Maxair MU532 accident near Vicksburg, Michigan, January 28, 1990

On January 28, 1990 at about 6:33 pm local time, a Maxair MU532, registered UNREG, was destroyed in an accident near Vicksburg, Michigan. It was a personal flight under general aviation rules (Part 91). 2 people were seriously injured. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

THE PILOT'S FAILURE TO MAINTAIN ADEQUATE AIRSPEED WHILE PERFORMING MANUEVERS.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
January 28, 1990 · about 6:33 pm local time
Place
Vicksburg, Michigan · map
Type
Accident
Injuries
2 people were seriously injured.
Weather
visual conditions (good weather)
Aircraft
Maxair MU532
Registration
UNREG · no longer on the register
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

THE PASSENGER REPORTED THEY WERE FLYING LOW AND SLOW WHILE CIRCLING HIS SISTERS HOUSE WHEN THE ACCIDENT OCCURRED. HE REPORTED BEING IN A LEFT TURN WHEN THE AIRCRAFT DESCENDED RAPIDLY TO IMPACT WITH THE TERRAIN. A WITNESS REPORTED THE PILOT WAS MAKING STEEP TURNS, DIVING AND CLIMBING PRIOR TO THE ACCIDENT. THE STUDENT PILOT HAD APPROXIMATELY 12 HOURS OF FLIGHT TIME.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

Pilot

  • Certificate: student
  • Flight time: 12 hours in all
  • Medical certificate: Class 2 (valid medical--no waivers/lim.)
  • Seat: frt

The aircraft

  • Last inspection: inspection type not recorded
  • Maximum gross weight: 900 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Rotax 532 (piston); 0 hours total

The flight

  • Departed from: Vicksburg MI
  • Flight plan: none
  • Runway 0

Weather at the time

  • Light: daylight
  • Wind: from 200° at 7 knots
  • Sky: not recorded; not recorded
  • Temperature: 37°F (3°C), dew point 12°F (-11°C)
  • Altimeter: 30.00 inHg
  • Observation at 6:45 pm from AZO, 8 miles away

Injuries

FatalSeriousMinorNone
Crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Other NTSB records under UNREG the same tail number, which may have belonged to a different aircraft at the time

2026-07-07CEN26LA246 · accident near Hooker, OK · substantial damage · minor injuries
2026-02-28CEN26LA131 · accident near Van Burensburg, IL · substantial damage · no injuries
2025-10-13ERA26LA017 · accident near Gaffney, SC · substantial damage · serious injuries
2025-09-27CEN25LA397 · accident near Harvard, IL · substantial damage · no injuries
2025-09-12CEN25LA385 · accident near Rossville, IN · substantial damage · serious injuries
2025-07-07CEN25LA242 · incident near Ingram, TX · minor damage · no injuries
2025-06-18DCA25WA305 · accident near N/A · serious injuries
2025-05-01OPS25LA034 · incident near Washington, DC
2025-04-11CEN25LA155 · accident near Brady, TX · substantial damage · serious injuries
2025-01-30DCA25MA108 · accident near Washington, DC · destroyed · fatal

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.