Freight Runners Express Flight 1544
Beech 99 · Accident: hard landing
From General Mitchell International Airport (MKE) to Central Wisconsin Airport (CWA)
Event
- NTSB case
- CHI04LA042
- 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
- Charter & commuter
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Beech 99
- Aircraft type
- Beechcraft 99
- 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
- N399CZ
- Operator
- Freight Runners Express
- Onboard fatalities
- Unknown
- Route
- From General Mitchell International Airport (MKE), Milwaukee, WITo Central Wisconsin Airport (CWA), Mosinee, 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 135: Air Taxi & Commuter
- 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
- Landing
- 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
- Hard landing
- 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 › Flare, inadequate
- Pilot in command › Proper descent rate, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane sustained substantial damage during a hard landing. The pilot stated, "On approach to rwy 8 at [Central Wisconsin Airport] I got high [and] right of course. When I broke out of clouds around 1000 [feet above ground level] I saw the runway, realizing I was high I pulled the power back [and] increased my rate of descent. I started to arrest my rate of descent [and] add power to keep my speed up. The engines didn't spool up in time resulting in a hard [landing]. I noticed the right wing was a little low taxing in so I thought maybe I blew a tire on landing. Not until I shut down [and] got out did I realize I hit the prop about an inch back [and] the engine nacelle dropped down several inches in front." The weather was: Wind 330 degrees at 8 knots; visibility 4 statute miles; present weather light snow; sky condition overcast 300 feet; temperature 1 degree C; dew point -1 degree C; altimeter 29.41 inches of mercury. The pilot reported that the flight did not have any mechanical malfunctions.
Probable cause
The pilot's failure to maintain the proper descent rate and his inadequate flare.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI04LA042
- Event ID
- 20031216X02050
- Case number
- CHI04LA042
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: 7264bf4b468ccad92233cd97ae437363fc9ce100d771ebada5d5637836af248d; retrieved 2026-09-18T15:33:04.720Z.