FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR25LA195 · Cessna 150F

28 Jun 2025 · Tracy, CA, United States

Cessna 150F · Accident: flight control system malfunction/failure during takeoff

From an unrecorded airport to Rancho Murieta Airport (KRIU)

Report a problem

Event

NTSB case
WPR25LA195
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
Ongoing
Event fatalities
Unknown
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 150F

Aircraft type
Cessna 150
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
N6744F
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo Rancho Murieta Airport (KRIU), Rancho Murieta, 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
Takeoff
Defining eventThe 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
Flight control system malfunction/failure
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

No findings designated as a cause are recorded in the NTSB data yet.

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

NTSB narrative

On June 28, 2025, about 1420 Pacific daylight time, a Cessna 150F, N6744F, was substantially damaged when it was involved in an accident at Tracy Municipal Airport (TCY), Tracy, California. The pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that she was enroute from Palo Alto, California to Rancho Murieta, California, and had landed at TCY to refuel. After completing a preflight, with no anomalies or concerns noted regarding the flight controls, the pilot decided to perform a soft field take-off for departure on runway 30. As the airplane lifted off the runway the pilot pitched the nose down to increase airspeed. The airplane drifted left, descended and impacted terrain adjacent to a taxiway. Postaccident examination of the airplane revealed that the right wing and engine mounts were substantially damaged.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record WPR25LA195
Event ID
20250630200428
Case number
WPR25LA195
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 0e5e3aa7e617f7e2a1ea56da600cc14ba560191f20675fd957ecf30fbf29f79c; retrieved 2026-09-16T20:01:30.299Z.