# Incident 20031211033989I: Gulstm 500B, Bloomington-Nor, IL, December 11, 2003

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: December 11, 2003, 03:45 local time
- Place: Bloomington-Nor, IL
- Airport: Bloomington-Normal
- Phase of flight: Normal Cruise
- Operating rules: Air taxi and commuter (Part 135)
- Operator: ZJWA
- Location: 40.4758° N, 88.9699° W: Placed by OpenAirDocs: center of Bloomington, IL, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=40.4758&lon=-88.9699&mi=10
- Aircraft: N615MT, registered now (https://openairdocs.org/aircraft/N615MT) (OpenAirDocs)
- Registry model: Aero Commander 500-B (registry code 0141106, https://openairdocs.org/model/aero-commander-500-b) (OpenAirDocs)
- Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs)
- Reported make and model: GULSTM 500B
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 1,440 total, 30 in this make and model, 250 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20031211033989I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) AIRCRAFT DEPARTED FROM CHICAGO MIDWAY ENROUTE TO ST. LOUIS LAMBERT AND WAS 5 MILES SOUTH OF BLOOMINGTON, IL AT 6000 FT WHEN AIRCRAFT STARTED TO EXPERIENCE ELECTRICAL FAILURE STARTING WITH THE HEATER, THEN LIGHTS, TRANSPONDER AND COMM RADIOS. CHICAGO CENTER HANDED THE AIRCRAFT OFF TO PEORIA, IL WHO HAD THE AIRCRAFT LAND IN BLOOMINGTON. THE AIRCRAFT LANDED WITHOUT INCIDENT AT 0400 EST.

## Other reports on N615MT (1)

Matched to the same aircraft by N-number and date.

- [Incident 20010329008339I](https://openairdocs.org/incident/20010329008339I), Mar 29, 2001: Gulstm 500B (N615MT), Bennett, CO. (-23) Upon arrival at the scene, aircraft was found without any damage. A visual inspection of the fuel tanks was made by inspectors from the denver FSDO and…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.