# NTSB NYC07CA014: Cessna 172N, N952AC, Morgantown, WV, October 29, 2006 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: October 29, 2006, 11:07 local (16:07 UTC) - Place: Morgantown, WV - Coordinates: 39.642776, -79.916389 - Nearby events: https://openairdocs.org/map.md?lat=39.6428&lon=-79.9164&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report February 26, 2007 - Report: Approved by Office Director - Parties: Charleston, WV - NTSB case key (mKey): 64773 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=NYC07CA014 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/64773/pdf - Page: https://openairdocs.org/ntsb/NYC07CA014 ## Probable cause The student pilot's failure to maintain directional control and the flight instructor's improper planning and supervision of the student's solo cross country flight. A contributing factor was the wind gusts. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of control - in flight, go-around (vfr) - directional control - not maintained, pilot in command (cause) - preflight planning/preparation - improper, flight instructor(on ground) (cause) - supervision - improper, flight instructor(on ground) (cause) - weather condition - gusts (contributing factor) - In flight collision with object, go-around (vfr) - object - tree(s) ## Analysis The student pilot departed from his home airport on a solo cross-country flight. He performed a "touch and go" at his first destination. He then proceeded to his second intended destination but, his first approach to the runway was "too high" so he executed a go around. He then attempted to land a second time. Due to "gusting winds," he was unable to land and elected to return to his home airport. Upon arriving at his home airport, he found that the wind was also gusting and his plane "floated" during the flare for landing. He attempted to go around, but the right wing "rose up" abruptly, the plane veered to the left, and struck trees. The student pilot's flight instructor reviewed the wind conditions prior to the student pilot's flight, and completed a logbook endorsement, which included a limitation of a 15-knot maximum headwind and 12-knot maximum crosswind. Winds at the approximate time of departure were forecast to be gusting to 25 knots. A weather observation made 15 minutes prior to the accident recorded the wind to be varying in direction 70 degrees, and gusting to 23 knots. ## Factual narrative The student pilot departed from his home airport on a solo cross-country flight. He performed a "touch and go" at his first destination. He then proceeded to his second intended destination but, his first approach to the runway was "too high" so he executed a go around. He then attempted to land a second time. Due to "gusting winds," he was unable to land and elected to return to his home airport. Upon arriving at his home airport, he found that the wind was also gusting and his plane "floated" during the flare for landing. He attempted to go around, but the right wing "rose up" abruptly, the plane veered to the left, and struck trees. The student pilot's flight instructor reviewed the wind conditions prior to the student pilot's flight, and completed a logbook endorsement, which included a limitation of a 15-knot maximum headwind and 12-knot maximum crosswind. Winds at the approximate time of departure were forecasted to be gusting to 25 knots. A weather observation made 15 minutes prior to the accident recorded the wind to be varying in direction 70 degrees, and gusting to 23 knots. ## Aircraft - Registration: [N952AC](https://openairdocs.org/deregistered/N952AC-2013-05-08), registration cancelled 2013-05-08, S/N 17268001, built 1976 (OpenAirDocs) - Reported make and model: Cessna 172N - Registry model: [Cessna 172N](https://openairdocs.org/model/cessna-172n) (registry code 2072434) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17268001 - Airframe hours: 10531.4 - Engines: Lycoming O-320-H2AD 160 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Registered owner: Flight Source LLC. - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, September 1, 2006, 22.7 hours before - Departed: PKB, Parkersburg, WV - Destination: MGW, Morgantown, WV - Airport: MGW, Morgantown Municipal Airport, runway 23, 2,769 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 46; injuries: none; student; medical: class 3, without waivers/limitations; seat: left; flight hours: 52 total, 52 in this make and model, 8 as pilot in command, 35 in the last 90 days, 10 in the last 30 days, 2 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 280° at 8 knots, gusting 23 - Visibility: 10 statute miles - Temperature: 50 °F, dew point 25 °F - Altimeter: 29.82 inHg - Observed at: MGW ## 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 20061029028829A](https://openairdocs.org/incident/20061029028829A), Oct 29, 2006: Cessna 172N, Morgantown, WV, Substantial damage. (-23) During approach to land on runway 23 at approximately 800 feet past the approach end of the runway, the student pilot lost control and veered to the left… ## Other investigations on N952AC (1) 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. - [NTSB MIA06CA009](https://openairdocs.org/ntsb/MIA06CA009), Oct 2, 2005: Cessna 172N (N952AC), Punta Gorda, FL, substantial damage. Probable cause: The in-flight collision with a bird resulting in substantial damage to the airplane. 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.