FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC10CA090 · Cessna 150L

11 Sept 2010 · Kenai, AK, United States Possible conflict

Cessna 150L · Accident: collision during takeoff/landing during initial climb

From Kenai, AK to Kenai, AK

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ANC10CA090
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 150L

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
N1612Q
Operator
Roni Carmon
Onboard fatalities
Unknown
Route
From Kenai, AKTo Kenai, AK
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
Initial climb
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
Collision during takeoff/landing
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The local personal flight was operating under Title 14 Code of Federal Regulations Part 91 when the accident occurred. The private pilot reported that he and a passenger were attempting to takeoff from a remote lake in his float-equipped airplane. During the initial climb, the airplane struck trees on the perimeter of the lake, became inverted in the trees, and caught fire. The pilot and passenger were not injured, but the airplane received structural damage to the fuselage and wings. The pilot was not certificated for seaplane operations, and noted in his report to the NTSB that he had probably overloaded the airplane prior to takeoff. He indicated there were no preimpact mechanical problems with the airplane.

Probable cause

The pilot's decision to takeoff from a remote lake after overloading the airplane. Contributing to the accident was the pilot's lack of a seaplane rating.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC10CA090
Event ID
20100914X82609
Case number
ANC10CA090
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2010-09-12.
  • API snapshot SHA-256: 08ef5950e82c75703f976802aca64f13a7b5a61143e51d50cae51d4c84492eca; retrieved 2026-09-15T15:12:37.477Z.