FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI07CA103 · Cessna 172S

14 Apr 2007 · Naples, FL, United States

Naples Air Center Cessna 172S · Accident: loss of control on ground/water during landing

From Naples Municipal Airport (APF) to an unrecorded destination

Report a problem

Event

NTSB case
CHI07CA103
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 172S

Aircraft type
Cessna 172
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N967SP
Onboard fatalities
Unknown
Route
From Naples Municipal Airport (APF), Naples, FLTo not recorded
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control on ground/water
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Pilot in command › Directional control, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane veered off the left side of the runway during landing and hit a runway marker sign. The pilot reported that the airplane touched down on runway 14 (5,000 feet by 100 feet, asphalt) with "left aileron in" and "slight" right rudder because winds were from approximately 110 degrees magnetic. After touchdown, she applied full engine power and additional right rudder because the airplane was not established on the runway centerline. The airplane veered to the left and the pilot "reduced power to idle and braked." The right main landing gear collided with a runway marker sign which caused the gear assembly to separate from the airplane. The left brake, nose wheel steering and rudder operation were tested and found to operate as designed.

Probable cause

The pilot's failure to maintain directional control of the airplane during landing. A contributing factor to the accident was the runway marker sign.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI07CA103
Event ID
20070508X00529
Case number
CHI07CA103
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 5af9aa5004b12823e505c437e018b293b95ef05d4c18392cd6e421f6ee85066a; retrieved 2026-09-22T03:54:23.547Z.