# NTSB DEN08CA087: Cessna 172H, N3870R, Brookshire, TX, May 11, 2008 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: May 10, 2008, 23:30 local (May 11, 2008, 04:30 UTC) - Place: Brookshire, TX - Coordinates: 29.838054, -95.949447 - Nearby events: https://openairdocs.org/map.md?lat=29.8381&lon=-95.9494&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Defining event: [Initial climb: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report June 30, 2008 - Report: Approved by Office Director - NTSB case key (mKey): 68007 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=DEN08CA087 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/68007/pdf - Page: https://openairdocs.org/ntsb/DEN08CA087 ## Probable cause The pilot's decision to duck under marked transmission lines and his failure to maintain clearance from the fence. Contributing to the accident was the marked transmission lines. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: altitude](https://openairdocs.org/ntsb-findings/01062012): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172H, 4 cases](https://openairdocs.org/ntsb-findings/01062012/cases.md?model=2072424), [All aircraft, 1,310 cases](https://openairdocs.org/ntsb-findings/01062012/cases.md) - [Experience/qualifications: qualification/certification](https://openairdocs.org/ntsb-findings/02031010): Personnel issues › Experience/knowledge · Pilot; cases with it: [Cessna 172H, 2 cases](https://openairdocs.org/ntsb-findings/02031010/cases.md?model=2072424), [All aircraft, 280 cases](https://openairdocs.org/ntsb-findings/02031010/cases.md) - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 172H, 10 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=2072424), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md) - [Object/animal/substance: wire](https://openairdocs.org/ntsb-findings/03022032): Environmental issues › Physical environment · Contributed to outcome (probable cause); cases with it: [Cessna 172H, 1 case](https://openairdocs.org/ntsb-findings/03022032/cases.md?model=2072424), [All aircraft, 588 cases](https://openairdocs.org/ntsb-findings/03022032/cases.md) - [Object/animal/substance: fence/fence post](https://openairdocs.org/ntsb-findings/03022047): Environmental issues › Physical environment · Not specified; cases with it: [Cessna 172H, 1 case](https://openairdocs.org/ntsb-findings/03022047/cases.md?model=2072424), [All aircraft, 313 cases](https://openairdocs.org/ntsb-findings/03022047/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Initial climb: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470) (defining event); cases with it: [Cessna 172H, 20 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072424), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The unqualified private pilot was practicing visual approaches and landings on a dark night. On his fourth or fifth pattern, the airplane was taking off following a full-flap touch-and- go when it struck a fence and impacted in a field past the departure end of the runway. The pilot stated he landed about one-third down the 4,100 foot runway and the roll out was longer than normal, but elected to attempt another approach. During climb out the pilot saw the orange marker balls on the power lines off the departure end of the runway, realized he could not clear them, and was attempting to dive under the wires when the airplane struck the fence. The pilot also stated the airplane was operating normally at the time of the accident and there were no engine or flight control malfunctions. Examination of the airplane revealed the right wing spar was bent upward. The pilot had not completed a biannual flight review within the past 24 months and did not meet currency requirements for carrying passengers as required by Federal Aviation Regulations. ## Factual narrative The private pilot was practicing visual approaches and landings on a dark night with one non-rated passenger. On his fourth or fifth pattern, the airplane was taking off following a full-flap touch and go when it struck a fence and impacted in a field past the departure end of the runway. The pilot stated he landed about one-third down the 4,100 foot runway and the roll out was longer than normal, but elected to attempt another approach. During climb out the pilot saw the orange marker balls on the power lines off the departure end of the runway, realized he could not clear them, and was attempting to dive under the wires when the airplane struck the fence. The pilot also stated the airplane was operating normally at the time of the accident and there were no engine or flight control malfunctions. Examination of the airplane revealed the right wing spar was bent upward. Information provided by the pilot on the Pilot/Operator Accident/Incident Report shows the pilot's last flight review was 1 April, 2006. Title 14 Code of Federal Regulations, Part 61.56 states a pilot must accomplish a flight review within 24 months of their last flight review in order to act as pilot in command. According to Federal Aviation Administration officials, the pilot failed to meet the currency requirements for carrying passengers as stated in Title 14 Code of Federal Regulations, Parts 61.57(a)1 and 61.57(b)1. ## Aircraft - Registration: [N3870R](https://openairdocs.org/deregistered/N3870R-2017-04-04), registration cancelled 2017-04-04, S/N 17255370, built 1966 (OpenAirDocs) - Reported make and model: Cessna 172H - Registry model: [Cessna 172H](https://openairdocs.org/model/cessna-172h) (registry code 2072424) (OpenAirDocs) - Registry engine: [Continental 0-300 series](https://openairdocs.org/engine/continental-0-300-series) (registry code 17022, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17255370 - Airframe hours: 2762 - Engines: Continental O-300 reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: First Takeoff, LLC - Airworthiness certificate: Standard, Normal - Last inspection: Annual, February 1, 2008 - Departed: Brookshire, TX - Airport: 27XS, Sports Flyer Estates, runway 17, 4,100 × 150 ft, grass/turf ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 55; injuries: none; private; airplane ratings: single-engine land; medical: class 3; seat: left; flight hours: 500 total, 75 in this make and model, 450 as pilot in command, 3 in the last 90 days, 2 in the last 30 days ## Weather - Conditions: Visual (VMC), Night/dark - Wind: calm - Temperature: 75 °F ## 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 20080510833649A](https://openairdocs.org/incident/20080510833649A), May 10, 2008: Cessna 172H, Brookshire, TX, Substantial damage. (-23) On may 10, 2008, at 2330 CDT, a Cessna 172H, N3870R, was substantially damaged when it overshot runway 17 while conducting touch and go night landings at… 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.