FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI03IA108 · Piper PA-31T1

17 Apr 2003 · Wheeling, IL, United States

Travel Express Aviation Piper PA-31T1 · Incident: in flight collision with object on approach

From Dupage Airport (DPA) to Chicago Executive Airport (PWK)

Report a problem

Event

NTSB case
CHI03IA108
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
Incident
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-31T1

Aircraft type
Piper PA-31
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
N855JL
Onboard fatalities
Unknown
Route
From Dupage Airport (DPA), West Chicago, ILTo Chicago Executive Airport (PWK), Wheeling, 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
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
Utility pole
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Flightcrew › Clearance, not maintained
  • Flightcrew › Proper glidepath, 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 flying club operated rental airplane was on short final approach to the destination airport when it impacted a 25-foot high unlighted utility pole 750 feet from the landing threshold. The left seat pilot's business flight was to pick up two passengers and then proceed to another destination. The electrical lines spanning the utility poles were equipped with red and white balls with reflective tape. Civil twilight with visual meteorological conditions prevailed at the time of the accident. The power line poles were not equipped with obstruction lights, but the lower traffic light poles had obstruction lights. The presence of poles was cited in the Airport Facility Directory, a publication to be used by pilots in flight planning. The landing runway was the shortest and narrowest of the runways at the airport. The Instrument Flying Handbook states this can create an illusion that the aircraft is at a higher altitude than it actually is, especially when runway length-to-width relationships are comparable. The airplane was piloted by a club member/instructor seated in the left seat with the club's president in the right seat who was a rated pilot and certified flight instructor. The left seat pilot was reported by both to be the flying pilot with the club's president working the radios and performing non-flying pilot duties as he did on previous flights. The right seat pilot stated that during the approach, the radar altimeter indicated an altitude of 200 feet above ground level two miles from the landing runway. At that time the right seat pilot reportedly pulled on the yoke and said no lower until we are at the "fence." A few seconds later after the right seat pilot released the controls, he felt a "bump." During an interview, the left seat pilot said that he had not been checked out in the incident airplane and could not cite what requirements for such a checkout would be. He had a total flight time of 9 hours in the incident airplane at the time of the incident. He initially stated that the club's president was serving as a "flight instructor, safety pilot, or whatever." The club's president reported a total flight time of 193 hours in the incident airplane. He later stated that the flight as others previously through the flying club were charter flights. The flying club did not hold a Federal Aviation Administration issued air carrier certificate.

Probable cause

The pilot's failure to maintain obstacle clearance and the inadequate glidepath which resulted in a collision with a utility pole. Contributing factors were the lack of experience in the incident airplane by the left seat pilot, the visual illusion of a narrower runway, inadequate crew coordination of both pilots, and the improper use of aircraft by the flying club's management. The unlighted utility pole and the civil twilight light conditions were additional factors.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI03IA108
Event ID
20030418X00532
Case number
CHI03IA108
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: e54c5a658ff9398255ac228ae904dd0684b3cd1fadc9a3980979b839f61a5b92; retrieved 2026-09-22T09:23:44.734Z.