# NTSB NYC07CA082: Cessna 172P, N96319, Sanford, FL, March 18, 2007

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: March 18, 2007, 15:03 local (19:03 UTC)
- Place: Sanford, FL
- Coordinates: 28.781665, -81.235
- Nearby events: https://openairdocs.org/map.md?lat=28.7817&lon=-81.2350&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report June 27, 2007
- Report: Approved by Office Director
- Parties: FAA/FSDO
- NTSB case key (mKey): 65447
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=NYC07CA082
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/65447/pdf
- Page: https://openairdocs.org/ntsb/NYC07CA082

## Probable cause

The student pilot's failure to maintain directional control during the landing roll.  Factors included a 90-degree crosswind, and the student pilot's improper in-flight decision to land on a runway with the crosswind rather than on an available runway with a headwind.

## Sequence of events

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

- Loss of control - on ground/water, landing - roll
  - weather condition - crosswind (contributing factor)
  - directional control - not maintained, pilot in command (cause)
  - in-flight planning/decision - improper, pilot in command (contributing factor)
- On ground/water collision with object, landing - roll
  - object - sign

## Analysis

The student pilot was returning to his home airport in a Cessna 172P after an uneventful cross-country flight, and attempting to land on runway 27R when the accident occurred.  Winds, about the time of the accident, were reported as 360 degrees true at 14 knots, gusting to 17 knots.  After touchdown, the airplane veered to the left, went off the runway, and impacted a sign.  Runway 36 was available for landing.  No mechanical anomalies were noted with the airplane.

## Factual narrative

According to the operator and a Federal Aviation Administration inspector, the student pilot was returning to his home airport in a Cessna 172P after an uneventful cross-country flight, and attempting to land on runway 27R when the accident occurred.  Winds, about the time of the accident, were reported as 360 degrees true at 14 knots, gusting to 17 knots.  After touchdown, the airplane veered to the left, went off the runway, and impacted a sign.  Runway 36 was available for landing.  No mechanical anomalies were noted with the airplane.

## Aircraft

- Registration: N96319 (not matched to a registry record)
- Reported make and model: Cessna 172P
- Category: Airplane
- Serial number: 17276056
- Engines: Lycoming O-320 reciprocating
- Damage: Substantial damage
- Flight: Instructional, Part 91
- Operator: Avion Air Academy, LLC
- Registered owner: Avion Air Academy, LLC
- Airworthiness certificate: Standard, Normal
- Departed: OCF, Ocala, FL
- Destination: SFB, Orlando, FL
- Airport: SFB, Orlando Sanford, runway 27R, 9,600 × 150 ft, concrete

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Student pilot; age 53; injuries: none; student; medical: class 3; flight hours: 75 total, 75 in this make and model, 20 in the last 90 days, 10 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: 360° at 14 knots, gusting 17
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 70 °F, dew point 30 °F
- Altimeter: 30.21 inHg
- Observed at: SFB

## 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 20070318005569A](https://openairdocs.org/incident/20070318005569A), Mar 18, 2007: Cessna 172P, Orlando, FL, Substantial damage. (-23) The student pilot was completing his first solo cross-country flight with a landing at Orlando Sanford international airport (ksfb) where he was vectored…

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.