16 Jan 2017: TEXTRON AVIATION INC 525C

16 Jan 2017: TEXTRON AVIATION INC 525C (N525PZ) — Unknown operator

No fatalities • Howell, MI, United States

Probable cause

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

— NTSB Determination

Accident 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.

Contributing factors

  • cause Pilot
  • cause Capability exceeded
  • cause Ability to respond/compensate
  • factor Availability of related info
  • factor Airport
  • factor Airport personnel
  • factor Airport personnel

Conditions

Weather
VMC, wind 130/04kt, vis 3sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.