CHI06CA054 · Piper PA-44-180
Windy City Flyers Piper PA-44-180 · Accident: hard landing
From Chicago Executive Airport (PWK) to an unrecorded destination
Event
- NTSB case
- CHI06CA054
- 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
Piper PA-44-180
- Aircraft type
- Piper PA-44
- 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
- N2196B
- Operator
- Windy City Flyers
- Onboard fatalities
- Unknown
- Route
- From Chicago Executive Airport (PWK), Chicago/Prospec, ILTo not recorded
- 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
- 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall
- 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
- Dual student › Airspeed, low
- Dual student › Proper descent rate, not maintained
- Flightcrew › Go-around, delayed
- Pilot in command(cfi) › Remedial action, delayed
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 flight instructor and dual student were engaged in an instructional flight at the time of the accident. The flight instructor held a multi-engine airplane instructor rating and was providing training to the other pilot at the time of the accident. The dual student held a commercial pilot certificate with single and multi-engine airplane ratings, and a flight instructor certificate with a single-engine airplane rating. He was obtaining training in preparation for the multi-engine flight instructor rating at the time of the accident. The flight instructor stated that he intended for the student to execute a simulated forced landing on the remaining runway immediately after liftoff. He reported that he instructed the dual student to back taxi the full length of the runway. The tower subsequently cleared the flight for takeoff followed by an immediate landing. He noted that the dual student held the brakes and applied full engine power. Upon reaching full power, the student released the brakes and began the takeoff roll. After liftoff the student established the airplane in a climb at 88 [knots]. The instructor stated that upon reaching an altitude of 200 feet above ground level (agl), he instructed the student to "simultaneously reduce both throttles to idle while pitching for a landing attitude that maintain[ed] 88 [knots]. He reported that the resulting descent rate "did not appear favorable" so about 100 feet agl he "commanded" the dual student to execute a go-around. He noted that full engine power was applied, however, the descent continued until the airplane contacted the runway in a "flat attitude." It subsequently bounced back into the air. He recalled that the stall warning horn sounded shortly before runway contact. The flight instructor stated that he assumed control of the airplane at this point and decided to continue the go-around since the engines seemed to be producing full power. He noted that during the flight around the traffic pattern, the rudder and stabilator were "less responsive than usual." He subsequently executed a no-flap landing on the departure runway. A post accident inspection revealed that the fuselage skin on the left and right sides, forward of the windshield was buckled. The left main landing gear strut was bent aft approximately 90 degrees. Both engine propellers were in the feathered position. The blade tips were curled and twisted consistent with runway contact.
Probable cause
Failure of the commercial pilot (dual student) to maintain a proper descent rate and a safe airspeed during the simulated forced landing. Additional causes were the failure of the flight instructor and the dual student to initiate a go-around in sufficient time to prevent the hard landing and a failure by the flight instructor to provide timely remedial action, which allowed an unsafe condition to develop. A contributing factor was the inadvertent stall encountered prior to runway contact.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI06CA054
- Event ID
- 20060113X00074
- Case number
- CHI06CA054
- 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: a10d2e07d1b1ac4a33fe04f07ef8b620533156464ac6e0514262ea6587184a11; retrieved 2026-09-22T05:12:45.753Z.