The U.S. aircraft register, updated daily
Accidents · NTSB CEN23LA266 · Final report

Piper PA-28-181 accident near Howell, Michigan, June 24, 2023

On June 24, 2023 at about 2:30 pm local time, a 1977 Piper PA-28-181, registered N4008Q, was substantially damaged in an accident during approach (VFR pattern downwind) near Howell, Michigan (Livingston County Spencer J Ha airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A loss of engine power due to the formation of carburetor ice that resulted from the pilot’s delayed use of carburetor heat during the landing approach.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
June 24, 2023 · about 2:30 pm local time · cases in 2023
Place
Howell, Michigan · Livingston County Spencer J Ha · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA-28-181, built 1977 · all PA-28-181s on the register
Registration
N4008Q · no longer on the register · serial 28-7790468
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot reported that during a local flight, while in the traffic pattern, the airplane’s engine power decreased to 900 rpm. He attempted to restore engine power but was unsuccessful and attempted to make a forced landing to the runway. He landed on the grass about 1,000 ft short of the runway surface, bounced, and impacted the localizer antenna. The airplane sustained substantial damage to the fuselage and both wings. Postaccident examination of the engine and fuel systems revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. The weather conditions at the time of the accident were conducive to a serious accumulation of carburetor ice at glide power. The pilot reported that he used carburetor heat while attempting to restore engine power, but not before he made his descent in the traffic pattern and the loss of engine power. Based on the available information, the loss of engine power was likely due to carburetor ice accumulation. Additionally, the low altitude at which the loss of engine power occurred significantly reduced the amount of time available to the pilot to troubleshoot and restore engine power before the forced landing.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Landing area undershoot during emergency descent
  2. Collision with terrain or object (not controlled flight into terrain) during emergency descent
  3. Fuel related during approach (VFR pattern downwind) defining event

The NTSB's findings

  • Environmental issues › Conditions/weather/phenomena › Temp/humidity/pressure › Conducive to carburetor icing › Effect on equipment
  • Environmental issues › Physical environment › Object/animal/substance › Airport structure › Contributed to outcome
  • Personnel issues › Action/decision › Action › Delayed action › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 328 hours in all; 109 in this make and model; 10.2 in the last 90 days; 1.7 in the last 30 days; 241 as pilot in command
  • Last flight review: November 1, 2021
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Passenger

  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 5,335.7 hours
  • Last inspection: 100-hour inspection, June 24, 2023; 0.2 hours since
  • Maximum gross weight: 2,550 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-360A4M (piston); 5,335 hours total

The flight

  • Flight plan: VFR
  • Runway 31, 5,000 ft by 100 ft

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: broken clouds at 1,300 ft
  • Temperature: 72°F (22°C), dew point 68°F (20°C)
  • Altimeter: 29.96 inHg
  • Observation at 10:35 am from KOZW, 1 miles away

Weather report (METAR): KOZW 241435Z AUTO 00000KT 10SM BKN013 BKN085 OVC110 22/20 A2996 RMK AO2 T02200197

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Photographs from the investigation 2 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

5 documents, released by the NTSB on May 9, 2024. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Other NTSB records under N4008Q the same tail number, which may have belonged to a different aircraft at the time

2006-08-16CHI06CA239 · accident near Napoleon, MI · substantial damage · no injuries

Connections how this case links to the rest of the register

Aircraft
Place
Record

The whole map of how records connect · these connections as data: /graph/accident/CEN23LA266.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.