CHI04CA117

NTSB accident investigation · Piper PA-28RT-201 · DeKalb, IL · May 8, 2004

Accident · No injuriesData collectionFinal report
Date
May 8, 2004, 14:30 local (19:30 UTC)
Place
DeKalb, IL
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N81898Piper PA-28RT-201
Weather
Visual (VMC) · Day
Status
Completed · report July 29, 2004
Report
Approved by Office Director
Parties
Federal Aviation Administration - DuPage FSDO
FAA report
20040508008729A
Case key
59254

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The failure of the pilot and his flight instructor to identify the location of the relocated threshold and proper touchdown point, which resulted in the airplane striking the construction barricade while on approach. A factor to the accident was the construction barricade.

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

UndershootApproach - vfr pattern - final approach
Proper touchdown point - not identifiedFlightcrewCause
Airport facilities,runway/landing area condition - displaced threshold
In flight collision with objectLanding
Airport facilities,construction/sign/barrierFactor

Analysis

The airplane struck a runway construction barricade during a simulated forced landing on runway 20. The runway 20 threshold had been relocated 600 feet towards the departure end because of an on-going runway construction project. Both the first 600 feet of the existing runway surface and the new pavement were marked with yellow painted chevrons, indicating those portions of pavement were closed for landing, takeoff, and taxing. The pilot stated he felt the airplane "was not going to make a landing on the existing runway and would probably touchdown on a section of the new part of the runway." The pilot stated he increased the engine power in order to arrest the descent, but the airplane touched-down on the new pavement. According to the certified flight instructor (CFI), while en route his student monitored the automated surface observing system and noted "runway 20 had a 600 foot displaced threshold." Prior to the accident approach the pilot performed two approaches, both of which were made to the closed section of runway 20. The CFI reported that on the accident approach the airplane experienced a hard landing near the intersection of the new and existing pavement sections. The CFI stated that he did not notice any construction barricades positioned at the end of runway 20. The airport manager reported that a runway construction barricade, originally positioned at the intersection of the existing pavement and new pavement sections, was damaged on the day of the accident. The broken portions of the barricade were distributed in a way consistent with an airplane hitting the barricade on landing approach.

Factual narrative

On May 8, 2004, at 1430 central daylight time, a Piper PA-28RT-201, N81898, piloted by a private pilot, sustained substantial damage when it impacted a runway construction barricade during a simulated forced landing to runway 20 (4,401 feet by 100 feet, dry asphalt) at the DeKalb Taylor Municipal Airport (DKB), DeKalb, Illinois. Visual meteorological conditions prevailed at the time of the accident. The instructional flight was operating under the provisions of 14 CFR Part 91 without a flight plan. The pilot and his certified flight instructor (CFI) were not injured. The flight originated from DuPage Airport (DPA), West Chicago, Illinois, at 1320 and was practicing takeoff and landings at DKB at the time of the accident.

The runway 20 threshold had been relocated 600 feet towards the departure end because of an on-going runway construction project. Runway 2/20 was being extended and new pavement had been laid at the time of the accident. Both the first 600 feet of the existing runway surface and the new pavement were marked with yellow painted chevrons, indicating those portions of pavement were closed for landing, takeoff, and taxing. The relocated threshold line was positioned 600 feet from the original threshold and new runway identification numbers were painted at approximately the C2 taxiway intersection. The existing runway pavement was approximately five-inches higher than the new paved extension. There were four construction barricades positioned at the intersection of the existing and new pavement sections.

According to the pilot's written statement, during the simulated forced landing he felt the airplane "was not going to make a landing on the existing runway and would probably touchdown on a section of the new part of the runway." The pilot stated he increased the engine power in order to arrest the descent, but the airplane touched-down on the new pavement. The pilot reported the airplane bounced or became airborne enough to land a second time on the existing pavement. The pilot stated he reconfigured the airplane for takeoff during the landing roll. The pilot reported he then took off and flew back to DPA. The pilot noticed the airplane was damaged during a post-flight inspection at DPA.

According to the CFI's written statement, while en route to DKB his student monitored the DKB automated surface observing system (ASOS) and noted "runway 20 had a 600 foot displaced threshold." The CFI stated once they had entered the traffic pattern he noticed, "white arrows hand painted on the new section of runway was being added, indicating a displaced threshold." The CFI also reported there were two sets of runway identification numbers; one set at the original threshold position and the other just prior to the C2 taxiway intersection. The CFI told the student to perform a short-field landing, with a simulated 50-foot obstacle positioned at the "end of the existing pavement." The CFI stated the student landed and stopped the airplane prior to the first cross taxiway (C2), which was used to exit the runway. The CFI stated he then repositioned the airplane onto the runway and the student performed a soft-field takeoff starting at the C2 intersection. According to the CFI, the next approach was a simulated forced landing and engine power was reduced "abeam the end of the existing pavement." The CFI reported that during the approach it became evident that the airplane "was obviously not going to make the runway" and he instructed the student to perform a go-around. The CFI stated the next approach was also a simulated forced landing. The CFI reported, "On this approach it appeared that the aircraft would touchdown at or slightly beyond where the existing pavement began." The CFI also reported, "On very short approach [the student] increased the aircraft pitch attitude further and then applied a substantial amount of power although I noted that the aircraft continued to descend until we touched down with a fairly loud bang that I felt was consistent with a hard landing." The CFI stated that he did not notice any construction barricades positioned at the end of runway 20.

The DKB airport manager reported that a runway construction barricade, originally positioned at the intersection of the existing pavement and new pavement sections, was damaged on the day of the accident. The broken portions of the barricade were distributed in a way consistent with an airplane hitting the barricade on landing approach.

Aircraft

Registration
N81898
Reported as
Piper PA-28RT-201
Category
Airplane
Serial number
28R-8018064
Airframe hours
3,107.76
Engine
Lycoming IO-360-C1C6, 200 horsepower, reciprocating
Damage
Substantial damage
Flight
Instructional · Part 91
Registered owner
Fox Flying Club, Inc.
Airworthiness certificate
Standard, Normal
Last inspection
Annual · January 1, 2004 · 77.45 hours before
Departed
DPA · West Chicago, IL
Destination
DKB · DeKalb, IL
Airport
DKB · DeKalb Taylor Municipal, runway 20, 4,401 × 100 ft, asphalt

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew · 2

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
55
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Instrument ratings
Airplane
Medical
Class 3, Valid Medical--w/ waivers/lim
Last flight review
September 6, 2003
Seat
Left
Flight hours
438 total · 105 in this make and model · 379 as pilot in command · 23 in the last 90 days · 10 in the last 30 days · 2 in the last 24 hours
Role
Flight engineer
Age
60
Injuries
None
Certificate
Airline transport
Airplane ratings
Single-engine land, Multi-engine land
Instrument ratings
Airplane
Medical
Class 2, Valid Medical--w/ waivers/lim
Last flight review
November 25, 2002
Seat
Rear
Flight hours
6,280 total · 200 in this make and model · 6,022 as pilot in command · 82 in the last 90 days · 34 in the last 30 days · 6 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
200° at 20 knots, gusting 25
Visibility
10 statute miles
Lowest ceiling
None
Temperature
79 °F, dew point 63 °F
Altimeter
29.95 inHg
Observed at
DKB

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.