LAX06FA211 · Cessna 560
Cessna 560 · Accident: overrun during landing
From Montgomery-Gibbs Executive Airport (MYF) to Upland-Cable Airport (CCB)
Event
- NTSB case
- LAX06FA211
- 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
- 1 · 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 560
- Aircraft type
- Cessna 560
- 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
- N486SB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Montgomery-Gibbs Executive Airport (MYF), San Diego, CATo Upland-Cable Airport (CCB), Upland, CA
- 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
- Overrun
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Touchdown, incorrect
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 touched down at night about 1,400 feet down the 3,864-foot runway and overran the runway surface, coming to rest about 851 feet beyond the departure end. The pilot was operating the airplane using a single-pilot waiver that he obtained two months prior to the accident. The airplane was certified by the Federal Aviation Administration with a flight crew of two. The pilot was returning from a personal event with his family, and landing at his home airport when the accident occurred. Witnesses stated that the pilot’s approach into the airport was not consistent with previous approaches in which the airplane would touch down directly on the runway numbers. They also stated that they heard the thrust reversers deploy, and then return to the stowed position. The airplane flight manual states that once the thrust reversers have been deployed, a pilot should not attempt to restow the thrust reversers and take off. Two sink rate warnings were issued during the approach to landing which should have alerted the pilot of the unstabilized approach. Performance calculations showed that the airplane would have required an additional 765 to 2,217 feet of runway for a full stop landing.
Probable cause
The pilot's unstabilized approach to the runway and failure to obtain the proper touchdown point, which resulted in a runway overrun.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX06FA211
- Event ID
- 20060629X00851
- Case number
- LAX06FA211
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2006-06-25.
- API snapshot SHA-256: a912789e82cfcd735ea99619a33b69e99a0bdda6f34a34a45ff2709264730a6d; retrieved 2026-09-20T17:16:16.897Z.