# NTSB CEN15LA111: Cessna 172F, N7854U, Lowell, MI, January 19, 2015

- Type: NTSB accident investigation
- Classification: Accident · Serious injuries · Limited investigation · Final report
- Date: January 19, 2015, 17:30 local (22:30 UTC)
- Place: Lowell, MI
- Coordinates: 42.953887, -85.343887 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=42.9539&lon=-85.3439&mi=10
- Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping)
- Defining event: [Approach-VFR go-around: Loss of control in flight](https://openairdocs.org/ntsb-events/240)
- Highest injury: Serious injuries
- Injuries: 1 serious
- Status: Completed, report July 7, 2015
- Report: Approved by Office Director
- NTSB office: Central Region
- Parties: Textron Aviation, Continental Motors, Flight Standards District Office
- NTSB case key (mKey): 90624
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN15LA111
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/90624/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=90624
- Page: https://openairdocs.org/ntsb/CEN15LA111

## Probable cause

The student pilot’s loss of airplane control during a go-around after not applying sufficient engine power.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Student/instructed pilot (probable cause); cases with it: [Cessna 172F, 12 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072414), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)
- [Action: lack of action](https://openairdocs.org/ntsb-findings/02041030): Personnel issues › Action/decision · Student/instructed pilot (probable cause); cases with it: [Cessna 172F, 3 cases](https://openairdocs.org/ntsb-findings/02041030/cases.md?model=2072414), [All aircraft, 792 cases](https://openairdocs.org/ntsb-findings/02041030/cases.md)
- [Use of equip/info: use of equip/system](https://openairdocs.org/ntsb-findings/02063015): Personnel issues › Task performance · Student/instructed pilot (probable cause); cases with it: [Cessna 172F, 3 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md?model=2072414), [All aircraft, 1,391 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md)
- [Performance/control parameters: climb rate](https://openairdocs.org/ntsb-findings/01062035): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172F, 2 cases](https://openairdocs.org/ntsb-findings/01062035/cases.md?model=2072414), [All aircraft, 265 cases](https://openairdocs.org/ntsb-findings/01062035/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Approach-VFR go-around: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Cessna 172F, 3 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=2072414), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md)

## Analysis

The solo student pilot was attempting a full-stop landing. The student reported that, when he recognized that the touchdown point was too far down the runway, he initiated a go-around. He added that, during the go-around, he did not apply full power. Due to the low engine power setting, the airplane climbed very slowly. Concerned about trees off the end of the runway, the student initiated a crosswind turn at low altitude and subsequently lost control of the airplane, which then rapidly descended and impacted terrain. Examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation.

## Factual narrative

On January 19, 2015, about 1730 eastern standard time, a Cessna 172F airplane, N7854U, impacted terrain during a go-around at the Lowell City Airport (24C), Lowell, Michigan. The solo student pilot was seriously injured and the airplane was substantially damaged. The airplane was registered to and operated by Majestic Air under the provisions of 14 Code of Federal Regulations Part 91 as an instructional flight. Visual meteorological conditions prevailed for the local flight, which departed without a flight plan. The student stated that he was attempting a full stop landing and elected to go-around when he realized his anticipated touchdown point was too long for the 2,394 foot runway. During the go-around maneuver, the student stated that he did not apply full power due to disorientation, which included blurred vision and dizziness. The airplane climbed slowly and approached the end of the runway at low altitude. Concerned with trees near the end of the runway, the student began a crosswind turn at low altitude. The student subsequently lost control of the airplane, which descended rapidly and impacted terrain. A video taken by the flight instructor captured the accident sequence; this video and the flight instructor's observations paralleled the student perspective of a shallow climb with less than full engine power, followed by a crosswind turn at low altitude and rapid descent. Examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation.

## Aircraft

- Registration: [N7854U](https://openairdocs.org/deregistered/N7854U-2016-04-26), registration cancelled 2016-04-26, S/N 17251854, built 1964 (OpenAirDocs)
- Reported make and model: CESSNA 172F
- Registry model: [Cessna 172F](https://openairdocs.org/model/cessna-172f) (registry code 2072414) (OpenAirDocs)
- Registry engine: [Continental 0-300 series](https://openairdocs.org/engine/continental-0-300-series) (registry code 17022, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 17251854
- Year built: 1964
- Airframe hours: 4112
- Engines: CONT MOTOR 0-300 SER 145 horsepower reciprocating
- Damage: Substantial damage
- Flight: Instructional, Part 91
- Operator: Majestic Air
- Registered owner: Majestic Air
- Airworthiness certificate: Standard, Normal
- Last inspection: 100 hour, October 31, 2014
- Departed: 24C, Lowell, MI
- Destination: 24C, Lowell, MI
- Airport: 24C, Lowell City Airport, runway 30, 2,394 × 48 ft, asphalt
- Equipment: Stall warning system

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Student pilot; age 40; injuries: serious; student; medical: class 3, without waivers/limitations; seat: left; restraint: lap only; flight hours: 23 total, 23 in this make and model, 3 as pilot in command, 3 in the last 90 days, 1 in the last 30 days, 1 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Dusk
- Wind: 10° at 3 knots
- Visibility: 10 statute miles
- Lowest ceiling: 2,900 ft overcast
- Temperature: 32 °F, dew point 23 °F
- Altimeter: 29.96 inHg
- Observed at: KGRR, 9 nm away

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20150119000349A](https://openairdocs.org/incident/20150119000349A), Jan 19, 2015: Cessna 172F, Lowell, MI, Substantial damage. N7854U a Cessna 172F performed a go around after missing landing touch down zone, during the climb out aircraft stalled subsequently impacting the ground.

## Docket (2 files)

The files NTSB released with the investigation on April 16, 2015, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=90624. 3.7 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 3.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40425134&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF
- Certification of Party Representation (item 2, .PDF, 646 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40425158&FileExtension=.PDF&FileName=Certification%20of%20Party%20Representation-Redacted.PDF

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
