CHI05LA130 · Pilatus PC-6
Pilatus PC-6 · Accident: in flight collision with object on approach
From Sylvania Airport (C89) to an unrecorded destination
Event
- NTSB case
- CHI05LA130
- 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
Pilatus PC-6
- Aircraft type
- Pilatus PC-6
- 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
- N346F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sylvania Airport (C89), Sturtevant, WITo 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
- Approach · VFR pattern final
- 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
- In flight collision with object
- 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
- Tree(s)
- 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
- Other person › Visual lookout, inadequate
- Pilot in command › Clearance, 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 parachute jump plane was substantially damaged when it collided with a parachutist on final approach for landing. The pilot was not able to maintain directional control and the airplane impacted trees and terrain near the airport. The pilot stated that he was on final approach for landing, when a parachutist "made a rapid descent and accelerated from behind [his] right wing." The parachutist hit the right wing and the airplane entered an unrecoverable descending right turn, subsequently striking a tree line. The parachutist involved in the accident stated that he "couldn't quite make it to the landing area" because the "spot was a little long." He noted that as a result he intended to land in front of the hangar. He reported he did not hear or see the jump plane. The parachutist stated: "I have a very high performance canopy and I descended quickly over the [airfield]. I crossed the far north edge of the grass runway for only an instant. I came from above and when my canopy leveled out, I was in front of the right wing." The drop zone for experienced parachutists was located north of the turf runway and west of the hangar buildings. Jump planes normally used the adjacent turf runway for landing. Advisory Circular 90-66A, Recommended Standard Traffic Patterns and Practices for Aeronautical Operations at Airports without Operating Control Towers, stated: "When a drop zone has been established on an airport, parachutists are expected to land within the drop zone. . . . Pilots and parachutists should both be aware of the limited flight performance of parachutes and take steps to avoid any potential conflicts between aircraft and parachute operations." Helmet-mounted video cameras from the parachutist involved in the accident, as well as a second parachutist on the accident jump, revealed that both parachutists descended through a cloud prior to canopy deployment. Federal regulations stated that parachute operations may not be conducted "into or through a cloud."
Probable cause
Failure of the jump plane pilot to maintain clearance from the parachutist descent area/drop zone until assured that all jumpers had landed, and the parachutist's failure to maintain an adequate visual lookout for the jump plane during all phases of the jump. Contributing factors were the inability of the pilot to maintain directional control of the airplane after collision with the parachutist, the airplane's low altitude at the time of the collision, the parachutist, and the trees. An additional factor was the proximity of the runway to the drop zone.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI05LA130
- Event ID
- 20050602X00712
- Case number
- CHI05LA130
- 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: 9c27e9bbde1c5c762b17ca8167bb47d2466cc5ecc0e6b2eed6eaae9ca007b4fc; retrieved 2026-09-21T19:00:53.010Z.