FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Larry'S Flying Service Britten-Norman BN-2B-21 accident

19 Apr 1999 · KONGIGANAK, AK, United States

Britten-Norman BN-2B-21 · Accident: on ground/water collision with terrain/water during landing

From Birchwater Airport (AK85) to an unrecorded destination

Report a problem

Event

NTSB case
ANC99LA051
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

Britten-Norman BN-2B-21

Aircraft type
Britten Norman BN-2
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
N414JA
Onboard fatalities
Unknown
Route
From Birchwater Airport (AK85), KWIGILLINGOK, 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
On ground/water 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

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

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

NTSB narrative

The certificated airline transport pilot reported that prior to landing he did a visual inspection of the runway. He noted that the runway appeared wet in some areas, but within acceptable limits for landing. He said that during the final stages of the landing roll, while moving at a relatively slow ground speed, the airplane's nose wheel encountered a large, water and mud-filled hole. He said that his postaccident inspection revealed that the nose strut had been bent aft, about 20 degrees from its original position. A subsequent inspection of the runway revealed a large, water-filled hole about 15 inches deep, by 1 foot wide, and 20 feet long in the middle of the runway. The pilot noted that there were no preaccident mechanical anomalies with the airplane. A subsequent inspection revealed that the airplane sustained substantial damage to the nose wheel bulkhead.

Probable cause

The deep, water filled hole in the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC99LA051
Event ID
20001205X00409
Case number
ANC99LA051
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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: a47edf61875339f00af5153dedb566969182816913ba4e19bca8fe917407f311; retrieved 2026-09-18T16:57:12.856Z.
  • The NTSB's operator name is blank for N414JA; the operator shown is the name the NTSB's other records give its FAA operator code, FWRA.