CEN18LA062

NTSB accident investigation · Cessna 525A · Michigan City, IN · December 27, 2017

Accident · Minor injuriesClass 3 · LimitedFinal report
Date
December 27, 2017, 06:50 local (12:50 UTC)
Place
Michigan City, IN
Injuries
2 minor
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N525KTCessna 525A
Defining event
Landing-landing roll: Runway excursion
Weather
Visual (VMC) · Dawn
Status
Completed
Report
Approved by Office Director
Investigation class
Class 3
NTSB office
Central Region
Parties
Federal Aviation Administration; DPA FSDO, Textron Aviation
FAA report
20171227024329A
Case key
96540

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 improper decision to land on a snow-covered runway that had insufficient runway distance for the airplane to land with the contamination, which resulted in a runway overrun and impact with obstacles.

Findings · 5

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Info processing/decision: decision making/judgmentPersonnel issues › Action/decision · Flight crewCessna 525A: 1 caseAll aircraft: 3,098 casesProbable cause
Aircraft capability: landing distanceAircraft › Aircraft oper/perf/capability · Capability exceededCessna 525A: 1 caseAll aircraft: 68 casesProbable cause
Runway/land/takeoff/taxi surface: snow/slush/ice covered surfaceEnvironmental issues › Physical environment · Decision related to conditionCessna 525A: 1 caseAll aircraft: 219 casesProbable cause
Runway/land/takeoff/taxi surface: snow/slush/ice covered surfaceEnvironmental issues › Physical environment · Effect on operationCessna 525A: 1 caseAll aircraft: 219 casesProbable cause
Performance/control parameters: surface speed/brakingAircraft › Aircraft oper/perf/capability · Not attained/maintainedCessna 525A: 2 casesAll aircraft: 238 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

The pilot reported that, during the approach following a positioning flight, he saw that the runway had a light dusting of snow on it and that the airplane touched down on speed in the first 1,000 ft of the 4,100-ft-long runway. The copilot, who was the pilot flying, applied heavy braking, but there appeared to be no braking effectiveness, and the airplane did not slow down as expected. The pilot added that, when the airplane reached about two-thirds of the way down the runway, he knew that it was going to overrun the runway due to the loss of only half of its airspeed. He thought that if he aborted the landing, there was a small chance the airplane could become airborne within the remaining runway. The copilot added engine power to abort the landing, and the nose landing gear lifted off, but insufficient runway was remaining to take off. The copilot reduced the engine power to idle, and the airplane overran the runway and went through the airport fence and a guardrail, across a highway, and into a field. Postaccident examination revealed no flat spots or evidence of skidding on the landing gear tires. The flaps were found in the “ground flaps” position, which is not allowed for takeoff. No evidence of any pre-accident mechanical malfunctions or failures were found with the airplane that would have precluded normal operation. Based on an airplane weight of 11,000 lbs, the airplane’s stopping distance would have been about 4,400 ft. The flight crew’s improper decision to land on a snow-covered runway that was too short to accommodate the landing in such conditions led to a runway overrun and impact with obstacles.

Factual narrative

On December 27, 2017, at 0650 central standard time, a Cessna 525A airplane, N525KT, impacted an airport fence, highway barrier, and terrain during a landing overrun on runway 20 (4,100 ft by 75 ft, asphalt/dry snow) following an area navigation (RNAV) runway 20 approach at Michigan City Municipal Airport-Phillips Field (MGC), Michigan City, Indiana. The airplane sustained substantial damage. The pilot and copilot received minor injuries. The airplane was registered to Van E Aviation LLC and operated by Integrated Flight Resources Inc under 14 Code of Federal Regulations Part 91 as a positioning flight and was operating on an activated instrument flight rules flight plan. The flight originated from DuPage Airport (DPA), West Chicago, Illinois, at 0622 and was destined to MGC for a Part 135 on-demand passenger flight. The pilot stated the co-pilot was the flying pilot for the flight. About halfway to MGC, they noticed instrument meteorological conditions below them. They flew the MGC RNAV approach runway 20 and broke out of the clouds with "adequate time to see the runway lights." The pilot said the runway appeared to have a "light dusting of snow." He said the airplane touched down on speed within the first 1,000 ft of the runway. The co-pilot "immediately" deployed ground flaps, and the airplane began slowing down. There appeared to be no braking effectiveness when co-pilot braked "heavily." He said the airplane was not slowing down as he was accustomed. About 2/3rds down, he knew that the airplane was going to overrun the runway, and the airplane had not lost half its airspeed. He said there was a small chance to become airborne within the remaining runway distance if an aborted landing was performed. The pilot said that engine power was added for the aborted landing, and for a moment it appeared that the airplane was going to become airborne as the nose wheel landing gear lifted off, but there was not enough runway remaining. Engine power was reduced to idle as the airplane overran the runway and went through the airport fence, a guard rail, across US Highway 20, and into a field. A witness, who was driving westbound in the right lane of US Highway 20, stated he saw the airplane traveling toward the north, go through the fence and guard rail, and missed his car by no more than 5 ft. The airplane came to rest, facing north, in a corn field about 300 yards from the departure end of the runway 20. The left wing was separated near wing station (WS) 57.00 and the right wing leading edge sustained damage near WS 171.00. The vertical stabilizer sustained damage near water line 195.00. A post-accident examination revealed that there were no flat spots or evidence of skidding on the landing gear tires. The flaps were in the GROUND FLAPS POSITION. There were no mechanical anomalies that would have precluded normal aircraft operation. According to the airport manager, the soonest that airport personnel could perform a post-accident runway inspection wasabout two hours after the accident and it revealed about ¼ inch of snow on the runway. The Cessna 525A Aircraft Flight Manual shows an airplane at the gross landing weight (12,500 lbs) and weather conditions, the airplane needed about 2,540 ft to stop on a dry runway. The 525A Section VII Advisory Information indicates that the stopping distance with 1 inch of snow was 7,100 ft and with 2 inches of snow was 6,300 ft. According to the Federal Aviation Administration inspector from the DuPage Flight Standards District Office, the approximate stopping distance on a wet runway based upon an aircraft weight of 11,000 lbs was 4,400 ft. An alternate airport required under Part 91.169(a)(2), IFR flight plan: Information required, was not filed by the flight crew.

Aircraft

Registration
N525KT
Reported as
Cessna 525A
Category
Airplane
Serial number
525A-0058
Built
2002
Airframe hours
2,681
Engines
Williams FJ44-2C, turbo fanWilliams FJ44-2C, turbo fan
Damage
Substantial damage
Flight
Positioning · Part 91
Operator
Integrated Flight Resources Inc
Registered owner
Van E Aviation LLC
Airworthiness certificate
Standard, Normal
Departed
DPA · West Chicago, IL
Destination
MGC · Michigan City, IN
Flight plan
IFR
Airport
MGC · Michigan City Municipal Airpor, runway 20, 4,100 × 75 ft, asphalt

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 · 2

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
28
Injuries
Minor
Certificates
Commercial, Flight instructor, Airline transport
Airplane ratings
Single-engine land, Multi-engine land
Instrument ratings
Airplane
Medical
Class 1, With waivers/limitations
Last flight review
September 11, 2017
Seat
Right
Flight hours
3,200 total · 300 in this make and model
Role
Co-pilot
Age
27
Injuries
Minor
Certificates
Commercial, Flight instructor
Airplane ratings
Multi-engine land, Single-engine land
Instrument ratings
Airplane
Medical
Class 1, Without waivers/limitations
Last flight review
June 1, 2017
Seat
Left
Flight hours
2,020 total · 81 in this make and model

Weather

Conditions
Visual (VMC) · Dawn
Wind
290° at 5 knots
Visibility
4 statute miles
Lowest ceiling
1,900 ft broken
Temperature
9 °F, dew point 3 °F
Altimeter
30.64 inHg
Observed at
MGC

Docket · 17

The files NTSB released with the investigation on October 9, 2020, on NTSB’s docket system: statements, records, photos and specialists’ reports.

FAA reports on this event · 1

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