Three Mexican Nationals Killed in Hawker 800XP Crash Near Lansing Identified; NTSB Investigation Continues
Why It MattersBusiness-jet maintenance test flights draw the same post-accident scrutiny as revenue operations, putting MRO providers' flight-test protocols and anomaly data under investigator review alongside the aircraft's airworthiness history.
What happened
Bath Charter Township officials said Sunday, Oct. 19, 2025, that the three people killed in the Oct. 16 crash of a business jet near Lansing have been presumptively identified as Mexican nationals: Rodolfo Pimental Zamora of Mexico City, Francisco Javier del Moral Jimenez of Ciudad de Mexico, and Alvaro Espejo Rodriguez of Veracruz, Mexico. Officials said the identifications are based on information from the Mexican consulate and are described as "presumptive," with dates of birth not yet confirmed; Clinton County Chief Medical Investigator Michelle Fox said final identification awaits DNA and other forensic testing.
The aircraft was a Hawker 800XP registered in Mexico to Aerolíneas del Centro SA. Duncan Aviation, which had performed maintenance on the jet at its Battle Creek Executive Airport facility, said the aircraft was on a "stall flight" when it crashed in a wooded area south of Clark Road in Bath Charter Township. FlightAware data showed the plane departed Battle Creek heading south, then turned northeast toward Lansing, reaching approximately 15,000 feet before radar tracking ended, with speed dropping from 240-260 knots to 83 knots.
Bath Township Fire Chief Mark Koonter said crews had to cut a trail through the wooded site, with trucks reaching only a third of the way in and firefighters laying half a mile of hose. He said environmental contamination was found at the site and reported to Michigan EGLE, declining to specify its nature. Township Supervisor Ryan Fewins-Bliss said the FAA and NTSB are continuing the investigation, with investigators remaining on scene as of Sunday and the NTSB expected to remove aircraft debris to its facility. Duncan Aviation said it is "actively supporting" the agencies involved, with company president Mike Minchow saying the firm's focus is on "supporting the families and friends of the crew, our team members who worked on the aircraft, and anyone else touched by the tragic event."
Industry impact & what to watch
A maintenance-related test flight ending in a fatal crash places the event at the intersection of two investigative tracks: the airworthiness and maintenance history of the specific aircraft, and the operational decisions made during a post-maintenance flight profile. Both the FAA and NTSB are involved, and debris recovery to an NTSB facility typically precedes a preliminary report that establishes a factual timeline before any probable-cause determination.
For MRO providers, a crash occurring on a flight tied to their own facility draws scrutiny regardless of eventual findings, since investigators will examine maintenance records, the nature of the "stall flight" profile, and crew actions alongside the airframe's mechanical condition. The presence of reported environmental contamination at the crash site adds a parallel regulatory thread through state environmental authorities that runs independently of the aviation investigation.
What happens next will depend on confirmed identification through DNA testing, the NTSB's preliminary report, and whatever findings emerge from the environmental contamination reported to Michigan EGLE.
