# NTSB CHI04CA117: Piper PA-28RT-201, N81898, DeKalb, IL, May 8, 2004 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: May 8, 2004, 14:30 local (19:30 UTC) - Place: DeKalb, IL - Coordinates: 41.931667, -88.708335 - Nearby events: https://openairdocs.org/map.md?lat=41.9317&lon=-88.7083&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report July 29, 2004 - Report: Approved by Office Director - Parties: Federal Aviation Administration - DuPage FSDO - NTSB case key (mKey): 59254 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI04CA117 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/59254/pdf - Page: https://openairdocs.org/ntsb/CHI04CA117 ## 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 In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Undershoot, approach - vfr pattern - final approach - proper touchdown point - not identified, flightcrew (cause) - airport facilities,runway/landing area condition - displaced threshold - In flight collision with object, landing - airport facilities,construction/sign/barrier (contributing factor) ## 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](https://openairdocs.org/aircraft/N81898), registered now, S/N 28R-8018064, built 1980 (OpenAirDocs) - Reported make and model: Piper PA-28RT-201 - Registry model: [Piper PA-28RT-201](https://openairdocs.org/model/piper-pa-28rt-201) (registry code 7102818) (OpenAirDocs) - Registry engine: [Lycoming I0360 SER A&C](https://openairdocs.org/engine/lycoming-i0360-ser-a-c) (registry code 41511, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 28R-8018064 - Airframe hours: 3107.76 - Engines: 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 ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 55; injuries: none; 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 - Flight engineer; age 60; injuries: none; 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 (OpenAirDocs). - [Accident 20040508008729A](https://openairdocs.org/incident/20040508008729A), May 8, 2004: Piper PA28RT201, Dekalb, IL, Substantial damage. (-23) Mr. Low, the instructor, was simulating engine out landings with his student Mr. Godfrey at Dekalb airport, Dekalb, Illinois. Runway 20 at Dekalb airport… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.