LAX90LA118 · Cessna 172M
Paradise Flying Club Cessna 172M · Accident: overrun during landing
From Chico Regional Airport (CIC) to an unrecorded destination
Event
- NTSB case
- LAX90LA118
- 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
- 0
- 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 172M
- 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
- N13317
- Operator
- Paradise Flying Club
- Onboard fatalities
- Unknown
- Route
- From Chico Regional Airport (CIC), Chico, CATo 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 · 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
- Overrun
- 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 › Lowering of flaps, not selected
- Pilot in command › Proper touchdown point, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT MADE THE LANDING USING ONLY 20 DEGREES OF FLAPS. THE AIRCRAFT TOUCHED DOWN ABOUT ONE THIRD OF THE LENGTH OF THE RUNWAY AND HE APPLIED THE BRAKES. SHORTLY THEREAFTER, THE AIRCRAFT ENTERED A SKID, WHICH CONTINUED FOR THE LENGTH OF THE PAVEMENT UNTIL THE AIRCRAFT WENT OFF THE DEPARTURE END OF THE RUNWAY. A POLICE AIR UNIT IS BASED AT THE AIRPORT. ACCORDING TO THE UNIT PILOTS, ABOUT A 4 KNOT TAIL WIND EXISTED AT THE TIME THE AIRCRAFT LANDED. THE OFFICERS SAID STANDING WATER WAS PRESENT ON THE RUNWAY SURFACE DUE TO A RECENT RAINFALL, AND THEY EXAMINED THE RUNWAY AFTER THE ACCIDENT AND SAID THAT SKID MARKS WITH HEAVY RUBBER DEPOSITS WERE FOUND ON THE RUNWAY FOR A DISTANCE OF ABOUT 120 YARDS FROM THE DEPARTURE END. FAA INSPECTORS EXAMINED THE AIRCRAFT AND REPORTED THAT BOTH MAIN TIRES HAD EVIDENCE OF EXTENSIVE HEAT OVER A TYPICAL FOOT PRINT AREA ON THE TIRE TREAD. THE INSPECTORS NOTED THAT PORTIONS OF THE TREAD CROWN WERE MELTED IN A PATTERN SIMILAR TO REVERTED RUBBER HYDROPLANING.
Probable cause
THE PILOT'S DECISION NOT TO USE FULL FLAPS WHICH RESULTED IN A LONG LANDING ON A WET RUNWAY.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX90LA118
- Event ID
- 20001212X22744
- Case number
- LAX90LA118
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1990-03-15.
- API snapshot SHA-256: 52f66e866efd7090168e150938e14a10a0d330e7ac74af4447b76bd97c004adb; retrieved 2026-09-21T23:56:26.326Z.