FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Peninsula Airways Grumman G-21A incident

7 Jan 1993 · Akutan, AK, United States

Grumman G-21A · Incident: loss of control on ground/water during landing

From Tom Madsen (Dutch Harbor) Airport (DUT) to an unrecorded destination

Report a problem

Event

NTSB case
ANC93IA026
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
Incident
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

Grumman G-21A

Aircraft type
Grumman G-21
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
N22932
Onboard fatalities
Unknown
Route
From Tom Madsen (Dutch Harbor) Airport (DUT), Unalaska, 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
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
Minor

Cause areas

  • Pilot in command › Compensation for wind conditions, improper

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

NTSB narrative

THE PILOT STATED THAT JUST AFTER TOUCHING DOWN ON THE WATER, HE ENCOUNTERED A MICROBURST. HE ESTIMATED THAT THE WIND SPEED SUDDENLY CHANGED FROM ABOUT 15 TO 20 KNOTS TO 40 TO 50 KNOTS. THE LEFT WING FLOAT HIT THE WATER AND WAS TORN OFF. BECAUSE OF THE STRONG WINDS AND ROUGH WATER HE WAS UNABLE TO GET AIRBORNE OR TO TURN THE AIRPLANE. HE KEPT THE AIRPLANE HEADED INTO THE WIND AND BEACHED THE AIRPLANE ON THE OPPOSITE SIDE OF THE BAY. THE PILOT ALSO SAID THAT SUITABLE WEATHER CONDITIONS HAD BEEN REPORTED FOR THE LANDING AREA ABOUT ONE HALF HOUR EARLIER.

Probable cause

THE INCIDENT WAS CAUSED BY THE PILOTS IMPROPER COMPENSATION FOR THE WINDS. FACTORS WERE THE MICROBURST, THE ROUGH WATER, AND THE PILOT'S INADEQUATE EVALUATION OF THE WEATHER CONDITIONS.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC93IA026
Event ID
20001211X11640
Case number
ANC93IA026
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: 26c7582e4edba72a63f68832b9684867e22d3d4f72c623286fdf6db2c88ac458; retrieved 2026-09-18T18:41:53.363Z.