ERA Helicopters Aerospatiale AS-350-B2 accident
Aerospatiale AS-350-B2 and Federal Aviation Administrat'N Cessna 172RG · Accident: midair collision en route
Event
- NTSB case
- ANC98FA061
- 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
- 2 · 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
Aircraft 1 · Aerospatiale AS-350-B2
- Aircraft type
- Aerospatiale AS-350
- 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
- N187EH
- Operator
- Era Helicopters
- Onboard fatalities
- Unknown
- Route
- From 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
- En route · cruise
- 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
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Aircraft 2 · Cessna 172RG
- Aircraft type
- Cessna 172
- 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
- N4948V
- Operator
- Federal Aviation Administrat'N
- Onboard fatalities
- Unknown
- Route
- From Petersburg James A Johnson Airport (PSG), Petersburg, AKTo Juneau International Airport (JNU), 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 91: General Aviation
- 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
- En route · cruise
- 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
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Visual lookout, inadequate
- Pilot of other aircraft › Visual lookout, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The air tour helicopter was at 2,100 feet msl, and had just crossed a salt water channel when it collided with the airplane. The helicopter landed with substantial damage, and one injured passenger. The airplane was destroyed when it impacted water in the channel, and both pilot-rated occupants were fatally injured. An 18-inch portion of the airplane's right wing remained attached to the helicopter. None of the occupants of the helicopter saw the airplane prior to collision. The helicopter was on a standard tour route utilized by the company, and published in an FAA advisory pamphlet which the airplane occupants also had on board. The collision occurred at a location where the advised traffic route inbound to the Juneau airport crossed the helicopter's air tour route. The helicopter had completed crossing the channel, and was 100 feet above the upper limit of the recommended altitude for the crossing. The airplane was 100 feet above the lower limit of the recommended altitude for aircraft traveling west. This area has a high volume of VFR air tour, air taxi, and general aviation traffic. The area is uncontrolled, Class G, airspace, with no radar coverage. The helicopter pilot described the visibility as good. The helicopter pilot made traffic advisory radio transmissions on the common traffic advisory frequency (CTAF) for the area of the collision. This frequency was published in the Alaska Supplement, the FAA advisory pamphlet for the area, and the VFR sectional aeronautical chart. The airplane's radios were not tuned to this frequency. The helicopter was illuminated with pulsating landing lights, and high visibility strobes. The airplane was configured with high visibility strobe lights on the wing tips, and two, nose-mounted landing/taxi lights, and a red anti-collision beacon on the tail. The control switches for the anti-collision beacon was found 'ON.' The control switch for the strobe lights was found in the 'OFF' position. The position of the landing/taxi lights could not be determined. Neither pilot in the airplane had any record of flight experience in the Juneau area.
Probable cause
The failure of both command pilots to maintain an adequate lookout to see and avoid each other's aircraft. Factors associated with the accident were the other pilot's failure to follow published advisory procedures to monitor/issue position reports on the appropriate radio frequency, and his lack of familiarity with the geographic area.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC98FA061
- Event ID
- 20001211X09966
- Case number
- ANC98FA061
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1998-05-31.
- API snapshot SHA-256: bf8604d36914e018985ff92102c04a5b575ba9c66e5fe81eb6aeef2f7ecf1501; retrieved 2026-09-18T13:23:25.666Z.
- The NTSB's operator name is blank for N187EH; the operator shown is the name the NTSB records it doing business as.