Camai Air Piper PA-32-300 accident
Piper PA-32-300 · Accident: in flight encounter with weather on approach
From Toksook Bay Airport (OOK) to an unrecorded destination
Event
- NTSB case
- ANC92LA031
- 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
- 0
- 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
- Charter & commuter
- 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
Piper PA-32-300
- Aircraft type
- Piper PA-32
- 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
- N76RL
- Operator
- Camai Air
- Onboard fatalities
- Unknown
- Route
- From Toksook Bay Airport (OOK), TOKSOOK, AKTo not recorded
- 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 135: Air Taxi & Commuter
- 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
- Approach · VFR pattern final
- 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 encounter with weather
- 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 › Flight into known adverse weather, continued
- Pilot in command › Wind information, misjudged
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE ON FINAL APPROACH FOR LANDING, THE PILOT REPORTED THAT THE FLIGHT ENCOUNTERED TURBULENCE AND A STRONG CROSSWIND. THE PILOT CONTINUED THE APPROACH UNTIL THE FLIGHT WAS ON SHORT FINAL AND APPROXIMATELY 50 TO 80 FEET AGL WHEN THE AIRPLANE SUDDENLY BANKED APPROXIMATELY 60 DEGREES TO THE LEFT. THE PILOT TRIED TO CORRECT WITH FULL OPPOSITE CONTROLS AND FULL POWER; HOWEVER, THE LEFT WING STRUCK THE GROUND. THE PILOT REGAINED CONTROL OF THE AIRPLANE AND INITIATED A GO-AROUND. THE PILOT CONTINUED THE GO-AROUND AND LANDED WITHOUT FURTHER INCIDENT.
Probable cause
MISJUDGED WIND INFORMATION. FACTORS TO THE ACCIDENT WERE: TURBULENCE, CROSSWIND AND FLIGHT INTO KNOWN ADVERSE WEATHER.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC92LA031
- Event ID
- 20001211X14054
- Case number
- ANC92LA031
- 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. 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: 9c1004ff63e65b405ae057e4e1ffd787ff2fe92ed1b3631c4efb41781378b12b; retrieved 2026-09-18T18:48:28.898Z.