NTSB CAROL · Event
Event CEN17LA078
Registry · N525PZ
FAA Aircraft Registry record.
Make / Model
CESSNA 525C
Year of manufacture
2017 · 0 years old at event
Engine
WILLIAMS FJ44-4A
Seats / Engines
11 seats · 2 engines
Last airworthiness date
20170315
ADS-B equipped
Yes — Mode-S A69CDE
Registrant of record
ZELIFF AVIATION LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's attempted landing on the ice-covered runway, which resulted in a runway excursion and impact with terrain. Contributing to the accident was airport personnel's lack of training regarding issuance of NOTAMs
Factual narrative
On January 16, 2017, at 1159 eastern standard time, a Textron Aviation 525C, N525PZ, collided with the terrain following a loss of control on landing at the Livingston County Airport (OZW), Howell, Michigan. The private pilot received serious injuries. The airplane was substantially damaged by impact forces and a post impact fire. The airplane was registered to and operated by Zeliff Aviation, Inc., under the provisions of 14 Code of Federal Regulations Part 91 as a business flight. Visual meteorological conditions prevailed near the accident site and the flight was operated on an instrument flight rules flight plan. The flight originated from the Genessee County Airport (GCQ), Batavia, New York at 1057.The pilot reported that prior to the flight he checked the weather and Notices to Airmen (NOTAMs) on the Aviation Digital Data Services Meteorological Terminal Aviation Routine Weather Reports (ADD METAR) website. When preparing for the Instrument Landing System (ILS) runway 13 approach at OZW, the pilot listened to the Automated Terminal Information Service (ATIS) and he used the airplane's flight management system (FMS) to determine the landing performance data. The pilot stated the Next Generation Radar (NEXRAD) was showing rain in the area, but the onboard radar was not. He did not encounter any precipitation once he descended below the clouds. He then canceled his flight plan and continued the approach. The pilot stated he knew there was a possibility of there being ice on the runway, as the weather conditions were favorable for ice. He stated he decided to continue the approach making sure he was accurately flying the approach speeds and that he did not land long on the runway. He stated he was prepared to go-around if the runway was icy. In addition, he saw an airplane holding short on a taxiway at the end of the runway, which appeared to be waiting for him to land so that it could depart, and this led him to believe the runway condition was good. The pilot did not use the common traffic advisory frequency (CTAF) to inquire about the runway conditions. The pilot stated that upon touchdown, he applied the speed brakes and spoilers. Once the nose wheel touched down, he applied the brakes and realized he had no braking action. He retracted the speed brakes, spoilers and flaps and applied takeoff power. The airplane yawed to the left, so he reduced the power to idle and applied right rudder to correct the airplane's heading. The airplane continued off the runway where it contacted a fence, a ditch, and crossed a road prior to coming to rest. The pilot next recalled the airplane came to rest with him hanging upside down by the seatbelt. He crawled out of the airplane and noticed the wings had separated. The lineman who was working in the fixed base operator reported hearing the pilot announce that he was on the ILS approach and then again that he was on short final. He stated the airplane touched down prior to the taxiway A-2 turnoff, and he asked the pilot if he knew where he was going to park. He walked outside and noticed the airplane was near the east end of the runway. He recalled hearing the engine power increase followed by the impact and black smoke. The airplane that was sitting at the end of the runway was being taxied to a maintenance shop and was not going to takeoff. The pilot and mechanic in the airplane stated they saw the airplane during its approach which looked "normal." They stated the taxiways were icy and there was mist/light rain in the area. Another witness who saw the accident and assisted the pilot following the accident, stated the roads were covered with ice and "very slick." This witness stated that the sleet and freezing rain had started about an hour before the accident. The aircraft recording system (AReS II) data from the airplane was downloaded. The data showed the airplane was ½ mile from the runway at 200 ft above ground level at an airspeed of 110 knots, and that the airplane touched down near the approach end of the runway prior to veering to the left. After touching down, the throttles were advanced for a period of about 15 seconds, reduced, then advanced momentarily once again. The Model 525C landing performance data charts show that at a weight of 14,500 lbs, a landing reference speed (Vref) of 108 KIAS, and with no wind, the landing distance on a wet icy runway would have been about 13,625 ft. The length of runway 13 was 5,002 ft. A NOTAM had not been issued regarding the icy runway conditions at OZW. The airport manager stated he was not at the airport at the time of the accident, and that he was still trying to learn the new digital NOTAM manager system. The employee who was at the airport was authorized to issue NOTAMs, but had not yet been trained on the new system. Subsequent to the accident, the airport manager reported that the employees have been trained on inspecting runway conditions and issuing NOTAMs. After exiting the clouds during the landing approach at the uncontrolled airport, the private pilot of the small jet canceled his instrument flight plan with air traffic control. He stated that, although there was no precipitation when he exited the clouds, he suspected the runway may be icy due to the weather conditions. The pilot saw an airplane holding short on the taxiway at the end of the runway and assumed it was preparing to takeoff, which he stated led him to believe that the runway condition was good. Although the pilot announced his location and intentions on the airport's common traffic advisory frequency (CTAF), he did not inquire about the runway condition via CTAF/UNICOM. Witnesses reported that the approach looked normal. After touchdown, the pilot applied brakes and realized he had no braking action. He subsequently retracted the speed brakes, spoilers, and flaps, and added takeoff power. The airplane yawed to the left and the pilot reduced engine power to idle while applying rudder to correct the airplane's track. The airplane continued off the runway, where it traveled through a fence and across a road before coming to rest inverted. The pilot and mechanic seated in the airplane that was holding short of the runway during the landing reported that they were only taxiing to a maintenance facility and did not intend to take off. They reported that the taxiways were icy. A witness who assisted the pilot following the accident reported that the roads at the time were covered in ice and "very slick." Recorded data from the airplane showed that the pilot flew a stabilized approach and that the airplane touched down near the approach end of the runway; however, given the icy runway conditions, the airplane's landing distance required exceeded the available runway by more than 8,000 ft. Airport personnel had not issued a NOTAM regarding the icy runway conditions. The airport manager stated he was not at the airport at the time of the accident, and that he was still trying to learn the new digital NOTAM manager system. The employee who was at the airport was authorized to issue NOTAMs, but had not yet been trained on the new system. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Surface speed/braking-Capability exceeded - C
- C Environmental issues-Physical environment-Runway/land/takeoff/taxi surface-Snow/slush/ice covered surface-Ability to respond/compensate - C
- F Environmental issues-Physical environment-Runway/land/takeoff/taxi surface-Snow/slush/ice covered surface-Availability of related info - F
- F Organizational issues-Support/oversight/monitoring-Training-(general)-Airport - F
- F Personnel issues-Task performance-Use of equip/info-Use of automation-Airport personnel - F
- F Personnel issues-Task performance-Use of equip/info-Use of policy/procedure-Airport personnel - F
Verbatim from NTSB's published report. Source file
NTSB_2017_CEN17LA078.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (loss of control, runway excursion, go-around, maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Runway Excursion — SKYbrary Knowledge Base
SKYbrary runway excursion review — RE-OE (overruns) + RE-LO (lateral). Risk drivers: long landing, high approach speed, contaminated surface, tailwind, mis-set autobrakes.
- Embry-Riddle Scholarly Commons 2017 · Conference paper
Energy Safety Management: Mitigating Loss of Control Inflight
Under the new Airman Certification Standards (ACS), the Federal Aviation Administration (FAA) has mandated for the first time that private and commercial pilot candidates demonstrate understanding of …
- NTSB Aircraft Accident Reports 2002 · Accident report
Loss of Control and Impact with Pacific Ocean — Alaska 261
Alaska Airlines Flight 261 (MD-83) Pacific Ocean, January 31, 2000 — 88 fatalities. Definitive investigation of the Alaska 261 pitch-runaway-and-loss-of-control crash.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER)
A Scoping Review of Aviation Loss of Control Inflight Research
Loss of control – inflight (LOC-I) contributes to aircraft accidents at unacceptably high rates. Significant industry efforts and research have aimed to improve LOC-I prevention, detection, and recove…
- NASA NTRS 2025 · Conference Paper
A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
Browse the full corpus — academia portal ↗