The Nome plane crash remains a pivotal event in regional aviation history, highlighting the challenges of operations in remote Alaska. Investigators continue to draw lessons from this incident as the community reflects on safety improvements.
Below is a structured overview of key aspects, followed by detailed sections that explore people, context, and outcomes related to the crash.
| Date | Aircraft | Route | Fatalities | Investigating Body |
|---|---|---|---|---|
| August 27, 1977 | Douglas DC-6B | Anchorage to Nome | 3 of 47 onboard | NTSB |
| Flight number | Evergreen International 5302 | Scheduled cargo/passenger | Injuries | Alaska State Troopers |
| Departure airport | Ted Stevens Anchorage International | Weather conditions | Survivors | FAA |
| Crash location | Nome Airport vicinity | Contributing factors | Immediate rescue response | Local authorities |
Flight Path and Approach Context
Understanding the flight path and approach context helps clarify how environmental and technical factors intersected on the night of the crash. The crew faced low visibility and crosswinds that complicated the final descent into Nome.
Weather briefings had indicated marginal conditions, yet decision points around go-around criteria became critical. Investigators focused on whether crew procedures aligned with operating guidelines for instrument approaches in frontier airports.
People and Community Impact
Passenger backgrounds
Passengers on Evergreen International 5302 included travelers heading to remote villages for work, alongside local residents returning home. The mix underscored the vital role air transport plays in connecting isolated communities.
Rescue and first response
Local volunteers and Alaska State Troopers coordinated a rapid response, reaching the site despite challenging terrain and weather. Their actions limited the loss of life and provided initial medical care for survivors.
Investigation Findings and Safety Recommendations
The National Transportation Safety Board examined flight data, voice recordings, and weather evidence to determine root causes. Their report emphasized procedural gaps and environmental risks specific to high-latitude operations.
As a result, regulators updated instrument approach procedures and enhanced crew training requirements for carriers serving western Alaska routes. These measures aimed to reduce similar incidents by reinforcing decision-making protocols.
Aviation Safety and Operational Procedures
Pre-flight planning requirements
Operators were reminded to conduct thorough risk assessments, including alternate airports and fuel reserves for extended operations in low-visibility regions.
In-flight decision protocols
Pilots were advised to reinforce go-around discipline and cross-check approach minima, especially when weather reports fluctuate near minimums.
Key Takeaways and Recommendations
- Review and reinforce go-around criteria for marginal weather approaches.
- Enhance pre-flight risk assessments, especially alternate airports and fuel planning.
- Strengthen crew coordination and checklist discipline during critical phases.
- Continue community-focused emergency response training for remote regions.
FAQ
Reader questions
What was the aircraft type and operator involved in the Nome crash?
The aircraft was a Douglas DC-6B operated by Evergreen International as flight 5302.
How many people were on board and how many fatalities occurred?
There were 47 people onboard, with 3 fatalities reported during the incident.
What weather conditions were reported at the time of approach? Low visibility and crosswinds were documented, complicating the instrument approach into Nome. What long-term changes resulted from this crash?
Regulators updated instrument approach procedures and strengthened crew training for remote Alaskan airports.