FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR12LA292 · Sikorsky S-58B

24 Jun 2012 · Brewster, WA, United States

Versatile Investments Sikorsky S-58B · Accident: fire/smoke (non-impact) while maneuvering

From Anderson Field (S97) to Anderson Field (S97)

Report a problem

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

Event

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

Sikorsky S-58B

Aircraft type
Sikorsky S-58
Category
Helicopter
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
N9043N
Onboard fatalities
Unknown
Route
From Anderson Field (S97), Brewster, WATo Anderson Field (S97), Brewster, WA
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 137: Agricultural
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
Maneuvering · hover
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
Fire/smoke (non-impact)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial Possible conflict

Cause areas

  • Not determined › Not determined

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

As the helicopter lifted into a hover, the manifold pressure gauge indicated a significant increase and the pilot smelled smoke. The pilot set the helicopter back onto the ramp and observed smoke rolling up the side of the fuselage. He egressed the helicopter rapidly and noticed fire around the engine compartment. The magnesium-constructed airframe was subsequently consumed by fire; the origin of the fire could not be determined.

Probable cause

An in-flight fire during hover for reasons that could not be determined due to the extent of fire damage that subsequently consumed the structure.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR12LA292
Event ID
20120703X10127
Case number
WPR12LA292
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: investigation status, coordinates. 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: eafab39bb536591f0b6419aa214af0292cd87ab2785e6104b4d794efb962c156; retrieved 2026-09-15T18:43:21.687Z.