FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA02LA041 · Cessna 180

15 Feb 2002 · Pacific City, OR, United States

Cessna 180 · Accident: nose over during landing

From McMinnville Municipal Airport (MMV) to Pacific City State Airport (PFC)

Report a problem

Event

NTSB case
SEA02LA041
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 180

Aircraft type
Cessna 180
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
N2434C
Operator
Unknown
Onboard fatalities
Unknown
Route
From McMinnville Municipal Airport (MMV), McMinnville, ORTo Pacific City State Airport (PFC), Pacific City, OR
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 · landing roll
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
Nose over
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 › Compensation for wind conditions, inadequate

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

While landing on a 30 foot-wide runway in steady crosswind conditions, the aircraft encountered an unexpected gust of wind. Although the pilot tried to correct for the unfavorable wind conditions, his attempts to do so were not adequate to keep the aircraft from departing the side of the runway. After departing the runway surface, the aircraft encountered a swampy area, and nosed over in about nine inches of water. The pilot later realized that wind funneling between buildings and trees located alongside the runway had created a funnel effect that produced areas of crosswind gusts.

Probable cause

The pilot's inadequate compensation for local wind conditions during the landing roll. Factors include unfavorable winds, and a swampy area adjacent to the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA02LA041
Event ID
20020228X00288
Case number
SEA02LA041
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. 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: 87ed1de1865bb37724d585621fc963bf8d4cfddda65a5bd3c66b4dd322206925; retrieved 2026-09-22T11:07:28.626Z.