DCA03MA008

NTSB accident investigation · Beech King Air 100 · Eveleth, MN · October 25, 2002

Accident · FatalClass 1 · MajorFinal report
Date
October 25, 2002, 00:00 local (06:00 UTC)
Place
Eveleth, MN
Injuries
8 fatal
Damage
Destroyed
Phase of flight
Approach
Aircraft
N41BEBeech King Air 100
Weather
Instrument (IMC) · Day
Status
Completed · report March 30, 2004
Report
Board-adopted at Board Meeting
Investigation class
Class 1
NTSB office
Major Investigations Division
Safety recommendations
Yes
FAA report
20021025033389A
Case key
55940

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The flight crew's failure to maintain adequate airspeed, which led to an aerodynamic stall from which they did not recover.

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

Loss of control - in flightApproach - faf/outer marker to threshold (ifr)
Airspeed - not maintainedFlightcrewCause
StallFlightcrew
In flight collision with terrain/waterDescent - uncontrolled
Terrain condition - ground

Analysis

The Board's full report is available at http://www.ntsb.gov/publictn/publictn.htm.

On October 25, 2002, about 1022 central daylight time, a Raytheon (Beechcraft) King Air A100, N41BE, operated by Aviation Charter, Inc., crashed while the flight crew was attempting to execute the VOR approach to runway 27 at Eveleth-Virginia Municipal Airport, Eveleth, Minnesota. The crash site was located about 1.8 nautical miles southeast of the approach end of runway 27. The two pilots and six passengers were killed, and the airplane was destroyed by impact forces and a postcrash fire. The airplane was being operated under the provisions of 14 Code of Federal Regulations Part 135 as an on-demand passenger charter flight. Instrument meteorological conditions prevailed for the flight, which operated on an instrument flight rules flight plan.

Factual narrative

The Board's full report is available at http://www.ntsb.gov/publictn/2003/AAR0303.pdf

On October 25, 2002, about 1022 central daylight time, a Raytheon (Beechcraft) King Air A100, N41BE, operated by Aviation Charter, Inc., crashed while the flight crew was attempting to execute the VOR approach to runway 27 at Eveleth-Virginia Municipal Airport, Eveleth, Minnesota. The crash site was located about 1.8 nautical miles southeast of the approach end of runway 27. The two pilots and six passengers were killed, and the airplane was destroyed by impact forces and a postcrash fire. The airplane was being operated under the provisions of 14 Code of Federal Regulations Part 135 as an on-demand passenger charter flight. Instrument meteorological conditions prevailed for the flight, which operated on an instrument flight rules flight plan.

Aircraft

Registration
N41BE
Reported as
Beech King Air 100
Category
Airplane
Serial number
B-245
Engine
Pratt & Whitney Canada PT6A-28, 680 horsepower, turbo prop
Damage
Destroyed
Fire
On-Ground
Flight
Part 135
Operator
Aviation Charter Inc.
Airworthiness certificate
Standard, Normal
Departed
STP · St Paul, MN
Destination
EVM · Eveleth, MN
Flight plan
IFR
Airport
EVM · Eveleth-Virginia Muni, runway 27

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Co-pilot
Age
30
Injuries
Fatal
Certificate
Commercial
Last flight review
August 4, 2002
Seat
Right
Flight hours
701 total · 107 in this make and model · 160 as pilot in command · 69 in the last 90 days · 36 in the last 30 days · 1 in the last 24 hours

Weather

Conditions
Instrument (IMC) · Day
Wind
Calm
Visibility
3 statute miles
Lowest ceiling
700 ft overcast
Temperature
34 °F, dew point 32 °F
Altimeter
30.05 inHg
Observed at
EVM, 2 nm away

Docket · 175

The files NTSB released with the investigation on March 26, 2003, on NTSB’s docket system: statements, records, photos and specialists’ reports. 106 MB in all.

Materials Laboratory 15 - Factual Report 02-125 light bulbsItem 1 · .PDF · 53 KBMeteorology 5 - Factual Report of Group ChairmanItem 2 · .PDF · 1.6 MBMeteorology 5 - Addendum 1Item 3 · .PDF · 348 KBATC 3 - Factual Report of Group ChairmanItem 4 · .PDF · 57 KBATC 3 - Attachment 1 Transcripts PNM AFSSItem 5 · .PDF · 396 KBATC 3 - Attachment 2 Transcripts DLH ATCTItem 6 · .PDF · 1.5 MBATC 3 - Attachment 3 EVM VOR Runway 27 Approach ChartItem 7 · .PDF · 96 KBATC 3 - Attachment 4 Sectional ChartItem 8 · .PDF · 8.8 MBATC 3 - Attachment 5 DLH Airspace ChartItem 9 · .PDF · 74 KBATC 3 - Attachment 6 DLH MVA ChartItem 10 · .PDF · 41 KBATC 3 - Attachment 7 DLH Radar Video Map 4Item 11 · .PDF · 23 KBATC 3 - Attachment 8 Weather SequencesItem 12 · .PDF · 777 KBATC 3 - Attachment 10 Radar GraphicsItem 13 · .PDF · 236 KBATC 3 - Attachment 11 DLH Daily Record of Facility Operation, FAA Form 7230-4Item 14 · .PDF · 81 KBATC 3 - Attachment 12 DLH Facility/Incident Notification Record, FAA Form 8020-3Item 15 · .PDF · 88 KBATC 3 - Attachment 13 DLH Aircraft Accident/Incident Preliminary Notice, FAA Form 8020-9Item 16 · .PDF · 80 KBSurvival Factors 6 - Factual Report of Group ChairmanItem 17 · .PDF · 689 KBSurvival Factors 6 - Attachment 1Item 18 · .PDF · 14 photos · 4.4 MBSurvival Factors 6 - Attachment 2Item 19 · .PDF · 52 KBSurvival Factors 6 - Attachment 3Item 20 · .PDF · 973 KBOperational Factors Group Chairman's Factual ReportItem 21 · .PDF · 134 KBOperations Errata 1Item 22 · .PDF · 10 KBOperations - Errata 2Item 23 · .PDF · 9 KBOperations-Addendum 1Item 24 · .PDF · 13 KBOperations - Addendum 2Item 25 · .PDF · 8 KBOperations - Addendum 2 AttachmentItem 26 · .PDF · 137 KBOperations-Attachment 1Item 27 · .PDF · 5 KBOperations - Attachment 2Item 28 · .PDF · 203 KBOperations - Attachment 3Item 29 · .PDF · 72 KBOperations - Attachment 4Item 30 · .PDF · 112 KBOperations - Attachment 5Item 31 · .PDF · 219 KBOperations - Attachment 6Item 32 · .PDF · 83 KBOperations - Attachment 7Item 33 · .PDF · 258 KBOperations - Attachment 8Item 34 · .PDF · 143 KBOperations - Attachment 9Item 35 · .PDF · 121 KBOperations - Attachment 10Item 36 · .PDF · 383 KBOperations - Attachment 11Item 37 · .PDF · 73 KBOperations - Attachment 12Item 38 · .PDF · 73 KBOperations - Attachment 13Item 39 · .PDF · 345 KBOperations - Attachment 14Item 40 · .PDF · 125 KBOperations - Attachment 15Item 41 · .PDF · 112 KBOperations - Attachment 16Item 42 · .PDF · 214 KBOperations - Attachment 17Item 43 · .PDF · 106 KBOperations - Attachment 18Item 44 · .PDF · 340 KBOperations - Attachment 19Item 45 · .PDF · 119 KBOperations - Attachment 20Item 46 · .PDF · 111 KBOperations - Attachment 21Item 47 · .PDF · 62 KBOperations - Attachment 22Item 48 · .PDF · 149 KBOperations - Attachment 23Item 49 · .PDF · 1.4 MBOperations - Attachment 24Item 50 · .PDF · 1.5 MBOperations - Attachment 25Item 51 · .PDF · 982 KBOperations - Attachment 26Item 52 · .PDF · 44 KBOperations Attachment 1-1Item 53 · .PDF · 9 KBOperations Attachment 1-2Item 54 · .PDF · 17 KBOperations Attachment 1-3Item 55 · .PDF · 10 KBOperations Attachment 1-4Item 56 · .PDF · 15 KBOperations Attachment 1-5Item 57 · .PDF · 14 KBOperations Attachment 1-6Item 58 · .PDF · 11 KBOperations Attachment 1-7Item 59 · .PDF · 7 KBOperations Attachment 1-8Item 60 · .PDF · 22 KB
All 175 files on NTSB’s docket

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.