CHI03LA256 · Nicoson Antares MA-33
Nicoson Antares MA-33 · Accident: loss of engine power en route
From East Troy Municipal Airport (57C) to Palmyra Municipal Airport (88C)
Event
- NTSB case
- CHI03LA256
- 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
- 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
Nicoson Antares MA-33
- Aircraft type
- Nicoson ANTARES MA-33
- 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
- N246AN
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From East Troy Municipal Airport (57C), East Troy, WITo Palmyra Municipal Airport (88C), Palmyra, WI
- 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
- En route · cruise
- 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 engine power
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Distance/altitude, misjudged
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane was substantially damaged when it impacted a fence during a forced landing, following a reported loss of engine power. The pilot reported that while in cruise flight at 1,000 feet above ground level, he increased engine power and then the engine experienced a loss of power. The pilot stated he "misjudged the rate of descent and landed short of the pasture and hit a fence." An examination of the engine confirmed continuity throughout the engine. The electrical ignition system was functional and both carburetor bowls contained fuel. The propeller was removed and the engine was prepared for a test run. The engine started and ran at idle power without anomalies. A full throttle engine run was not performed, due to the lack of the propeller, however, the engine did respond to momentary throttle inputs.
Probable cause
The loss of engine power for undetermined reasons and the pilot misjudging the descent rate during the forced landing, which resulted in the airplane landing short of the desired landing area. A factor to the accident was the fence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI03LA256
- Event ID
- 20030818X01347
- Case number
- CHI03LA256
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: 3db4828fcc22946c87bd396091409d735839b35d405bf95bc600e93f41a21796; retrieved 2026-09-22T08:47:44.221Z.
- Corrected after a review of the NTSB narrative, which states these values explicitly: damage. The narrative states "The airplane was substantially damaged when it impacted a fence during a forced landing", not destroyed.