Homer Air Service Britten-Norman BN-2A accident
Britten-Norman BN-2A · Accident: on ground/water encounter with weather during takeoff
From Nanwalek Airport (KEB) to Homer Airport (HOM)
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ANC99LA006
- 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-2A Narrative disagrees
- 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
- N6522T
- Operator
- Homer Air Service
- Onboard fatalities
- Unknown
- Route
- From Nanwalek Airport (KEB), AKTo Homer Airport (HOM), Homer, 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 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
- Takeoff · roll/run
- 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 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 › Clearance, not maintained
- Pilot in command › Compensation for wind conditions, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane was departing runway 19, with winds from 240 degrees magnetic at 20 knots gusting to 25 knots, when it collided with an airplane parked across the east edge of the runway. No ramp area exists at the airport, requiring airplanes to park on the runway edge of the 1,850 feet long by 50 feet wide airstrip. The pilots of both airplanes told the NTSB investigator-in-charge that there was room to taxi past the parked airplane.
Probable cause
The pilot-in-command's inadequate compensation for the crosswind conditions, and failure to maintain adequate clearance from the parked airplane. Factors associated with this accident were the gusty crosswinds, and the congested takeoff area due to no parking ramp.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC99LA006
- Event ID
- 20001211X11191
- Case number
- ANC99LA006
- 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: 5fd4297d6311c2e8c8629c364980ae02715d68a49274f082a744f5005787d401; retrieved 2026-09-18T17:03:49.080Z.
- The NTSB's operator name is blank for N6522T; the operator shown is the name the NTSB records it doing business as.