LAX01LA102 · Cessna 172N
Plus One Flyers Cessna 172N · Accident: loss of control on ground/water during landing
From Scottsdale Airport (SDL) to Montgomery-Gibbs Executive Airport (MYF)
Event
- NTSB case
- LAX01LA102
- 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 172N
- 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
- N4922D
- Operator
- Plus One Flyers
- Onboard fatalities
- Unknown
- Route
- From Scottsdale Airport (SDL), Scottsdale, AZTo Montgomery-Gibbs Executive Airport (MYF), San Diego, 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 · 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
- 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
During landing rollout, the airplane veered off the runway and collided with obstacles. At the completion of a 3.7-hour-long flight, the tower controller advised the pilot that the local wind was from 270 degrees at 6 knots, and asked him to switch runways to the parallel. After touchdown, the airplane was still traveling about 50 knots when, approaching runway 28L's midfield location, the pilot lost directional control. The left wing rose upward. The airplane veered off the runway and impacted a sign. Airport personnel reported that the collision occurred about 1,000 feet upwind of the runway's threshold. The airplane came to a stop about 550 feet farther upwind of the sign and about 200 feet north of the runway. No mechanical malfunctions were reported with the airplane.
Probable cause
The pilot's failure to maintain directional control of the airplane during landing rollout.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX01LA102
- Event ID
- 20010227X00520
- Case number
- LAX01LA102
- 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: 4ddcc4f211b96d5387f8a7a2ec9e7fd8344c9fb3ea44194f1de7053746f19b64; retrieved 2026-09-22T12:09:43.875Z.