CEN11FA537 · Morrison E-RACER
Morrison E-RACER · Accident: loss of control in flight while maneuvering
From Aurora Municipal Airport (ARR) to Aurora Municipal Airport (ARR)
Event
- NTSB case
- CEN11FA537
- 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
- 1 · all aircraft and ground
- Ground fatalities
- Unknown
- 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
Morrison E-RACER
- Aircraft type
- Morrison E-RACER
- 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
- N345JM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Aurora Municipal Airport (ARR), Sugar Grove, ILTo Aurora Municipal Airport (ARR), Sugar Grove, IL
- 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
- Defining eventThe 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
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The accident occurred during the first flight test of the recently completed experimental amateur-built airplane. The tower controller cleared the flight to orbit the airport at 2,500 feet mean sea level (msl) and to make left turns. As the airplane was completing its first orbit of the airport, the pilot told the tower controller that the airplane was experiencing excessive engine cylinder head temperatures and that he would like to land. According to radar track data, the airplane was at 2,700 feet msl and had a ground speed of about 145 knots at that time. The tower controller replied that the wind was calm and that the flight was cleared to land. The pilot acknowledged the landing clearance, and no additional communications were received from the pilot. Radar track data indicated that the airplane began a left descending turn as its ground speed decreased from about 170 to 105 knots, and its descent rate increased from 650 to 2,400 feet per minute. The last radar return was about 2 miles west-southwest of the airport about 400 feet above the ground. A witness observed the accident airplane traveling about 125 feet above the ground at a high speed while in a slight left turn with its landing gear retracted. The airplane leveled its wings momentarily before it entered a left-wing-low, wings-near-vertical descent and then collided with power lines and a cornfield. The postaccident examination of the airplane revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. No evidence of an in-flight fire was found. The extent of damage to the engine compartment and associated baffling precluded a determination of why the engine developed excessive cylinder head temperatures during the accident flight. However, excessive engine cylinder head temperatures would not have resulted in a flight controllability issue and, therefore, the pilot should have been able to maintain control of the airplane throughout the flight. The pilot had accumulated about 365 hours of flight experience in a comparable airplane.
Probable cause
The pilot's failure to maintain airplane control after experiencing excessive engine cylinder head temperatures during the initial flight test of the experimental amateur-built airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN11FA537
- Event ID
- 20110802X13338
- Case number
- CEN11FA537
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 7714a2fa72bf1861b0b7922bc271328908465935ef75b455ab82f3c2bd2bd1da; retrieved 2026-09-13T21:41:02.495Z.