# NTSB DFW07CA210: Cessna 172, N364GW, McKinney, TX, September 28, 2007

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: September 28, 2007, 15:21 local (20:21 UTC)
- Place: McKinney, TX
- Coordinates: 33.177776, -96.590553
- Nearby events: https://openairdocs.org/map.md?lat=33.1778&lon=-96.5906&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report December 20, 2007
- Report: Approved by Office Director
- Parties: Dallas, Texas
- NTSB case key (mKey): 66902
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=DFW07CA210
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/66902/pdf
- Page: https://openairdocs.org/ntsb/DFW07CA210

## Probable cause

The student pilot's failure to compensate for existing conditions while landing.  A contributing factor was the prevailing crosswind.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Loss of control - on ground/water, landing - flare/touchdown
  - weather condition - crosswind (contributing factor)
  - compensation for wind conditions - improper, pilot in command (cause)
- Loss of control - on ground/water, landing - roll
  - aircraft control - not maintained, pilot in command

## Analysis

Prior to the 40-hour student pilot's first solo flight, the flight instructor supervised four touch-and-go landings.  The flight instructor received a report from the control tower of winds 40 degrees left of runway heading at 7 knots.  The flight instructor then approved the student pilot's solo flight requiring three full-stop taxi-back landings.  The student pilot performed a touch-and-go landing and entered the traffic pattern.  During the second landing on Runway 17, the airplane was observed by tower personnel to bounce, porpoise, contact the runway with the propeller, and finally depart the runway at approximately midfield.  In a statement to the NTSB, the student pilot appeared confused as why the airplane had a left turning tendency during takeoff and drift throughout the pattern.  On final approach, the student pilot reported making an aileron input for the crosswind.  The student pilot struggled to maintain control of the aircraft before departing the 100-foot wide runway and coming to rest in the grass.  The flight instructor was not able to witness either student landing but reported that the earliest landings were "good."  An inspection of the aircraft revealed structural damage to the aircraft's firewall.  No mechanical malfunction or failure was reported.  At the time of the accident the tower reported winds from 50 degrees left of runway heading at 8 knots.

## Factual narrative

Prior to the 40-hour student pilot's first solo flight, the flight instructor supervised four touch-and-go landings.  The flight instructor received a report from the control tower of winds 40 degrees left of runway heading at 7 knots.  The flight instructor then approved the student pilot's solo flight requiring three full-stop taxi-back landings.  The student pilot performed a touch-and-go landing and entered the traffic pattern.  During the second landing on Runway 17, the airplane was observed by tower personnel to bounce, porpoise, contact the runway with the propeller, and finally depart the runway at approximately midfield.  In a statement to the NTSB, the student pilot appeared confused as why the airplane had a left turning tendency during takeoff and drift throughout the pattern.  On final approach, the student pilot reported making an aileron input for the crosswind.  The student pilot struggled to maintain control of the aircraft before departing the 100-foot wide runway and coming to rest in the grass.  The flight instructor was not able to witness either student landing but reported that the earliest landings were "good."  An inspection of the aircraft revealed structural damage to the aircraft's firewall.  No mechanical malfunction or failure was reported.  At the time of the accident the tower reported winds from 50 degrees left of runway heading at 8 knots.

## Aircraft

- Registration: [N364GW](https://openairdocs.org/aircraft/N364GW), registered now, S/N 172S9364, built 2003 (OpenAirDocs)
- Reported make and model: Cessna 172
- Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs)
- Registry engine: [Lycoming IO-360-L2A](https://openairdocs.org/engine/lycoming-io-360-l2a) (registry code 41597, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 172S9364
- Airframe hours: 2882.3
- Engines: Lycoming IO-360-L2A 180 horsepower reciprocating
- Damage: Substantial damage
- Flight: Instructional, Part 91
- Operator: Monarch Air, doing business as Monarch Air
- Registered owner: HDH Aircraft Leasing LLC
- Airworthiness certificate: Standard, Utility; Standard, Normal
- Last inspection: 100 hour, August 1, 2007, 66 hours before
- Departed: ADS, DALLAS, TX
- Airport: TKI, Mc Kinney Muni, runway 17, 7,001 × 100 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Student pilot; age 22; injuries: none; student; medical: class 1, without waivers/limitations; seat: left; flight hours: 40 total, 40 in this make and model, 1 as pilot in command, 40 in the last 90 days, 20 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: 120° at 8 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 82 °F, dew point 61 °F
- Altimeter: 30.18 inHg
- Observed at: TKI

## 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 20070928823799A](https://openairdocs.org/incident/20070928823799A), Sep 28, 2007: Cessna 172S, Mc Kinney, TX, Substantial damage. (-23) During landing phase, student pilot bounced aircraft numerous times on main landing gear with final bounce on nose gear causing nose gear to collapse.…

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.
