FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX06LA205 · Cessna 177B

17 Jun 2006 · Redwood City, CA, United States

Cessna 177B · Accident: in flight collision with terrain/water en route

From Oakland San Francisco Bay Airport (OAK) to Palo Alto Airport (PAO)

Report a problem

Event

NTSB case
LAX06LA205
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 177B

Aircraft type
Cessna 177
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
N35058
Operator
Unknown
Onboard fatalities
Unknown
Route
From Oakland San Francisco Bay Airport (OAK), Oakland, CATo Palo Alto Airport (PAO), Palo Alto, 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
En route · descent
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
In flight collision with terrain/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

  • Reason for occurrence undetermined

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

NTSB narrative

The pilot said he had no recollection of the events that transpired during the accident sequence. He did recall that he cancelled flight following with the local air traffic controller, and noted the airplane's altitude as 1,300 feet above the water. The last thing he remembered was reaching down to change radio frequencies, and then he was waist deep in water near the shoreline. He waited for the airplane to sink for a couple of minutes, but the water level never rose. He opened the door and exited the airplane into about 4 feet of water, and was able to walk around until the Coast Guard arrived. The pilot was transported to the hospital with no injuries. There was no follow-up inspections to the airframe or engine.

Probable cause

A collision with water for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX06LA205
Event ID
20060705X00870
Case number
LAX06LA205
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: 3bfafe98564114526b74e3156a33070ff300461314609bc2c78345d6faa64966; retrieved 2026-09-22T04:45:45.466Z.