Cessna 172K accident near Spartanburg, South Carolina, September 20, 2024
On September 20, 2024 at about 7:43 pm local time, a 1969 Cessna 172K, registered N7037G, was substantially damaged in an accident during initial climb near Spartanburg, South Carolina (Spartanburg Downtown Memorial airport). It was a flight test under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
Maintenance personnel’s failure to follow the engine manufacturer’s maintenance guidance, which resulted in the assembly of the engine with an obstructed oil passage, a subsequent lack of lubrication to the front main bearing, and a total loss of engine power.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 20, 2024 · about 7:43 pm local time · cases in 2024
- Place
- Spartanburg, South Carolina · Spartanburg Downtown Memorial · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172K, built 1969 · all 172Ks on the register
- Registration
- N7037G · registry record · serial 17258737
- Damage
- Substantial damage
- Flight
- Flight test · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot was conducting a local “break-in” flight for the airplane’s recently-installed engine. During the initial climb, the engine’s rpm started to decline, followed by a total loss of engine power. The pilot performed a forced landing to a field and the airplane nosed over during the landing roll, resulting in substantial damage to the airplane’s fuselage, wings, rudder, and vertical stabilizer. A postaccident examination of the airplane revealed that the engine’s crankshaft was not free to rotate. The engine’s front main bearing was discolored and exhibited rotational abrasion at its rear oil passage area and corresponding crankshaft surface. Additionally, insect-related debris, soil/clay/mud, and lubricating oil were obstructing the crankcase oil header and the front main bearing’s aft oil passage. The signatures of lubrication distress observed on the front main bearing were consistent with oil starvation as a result of the obstructions found within the engine’s lubrication system. Review of the engine’s maintenance records showed that crankcase was repaired nearly 12 years before the accident and that the engine was overhauled 2 years later. The engine did not accrue any time in service prior to its installation on the accident airplane about 1 month before the accident (about 10 years after the overhaul). The mechanic who performed the engine overhaul reported that the crankcase was stored in a hangar for several months before he acquired it and that he did not remember cleaning and verifying that the oil passages of the crankcase were unobstructed before assembly. According to the engine manufacturer’s overhaul manual, all oil passages should be cleaned with suitable brushes then flushed thoroughly with clean solvent and compressed air. Based on the available evidence, an insect likely infiltrated the crankcase and made a nest in the oil passages during the more than 2 years it was stored. Maintenance personnel then failed to clean and verify the oil passages were free of obstruction before assembly of the engine, which resulted in a lack of lubrication to the front main bearing and a subsequent total loss of engine power.
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
- Loss of engine power (total) during initial climb defining event
- Nose over/nose down during landing (landing roll)
- Off-field or emergency landing during emergency descent
The NTSB's findings
- Aircraft › Aircraft power plant › Engine (reciprocating) › Recip engine power section › Inadequate inspection other cases naming the engine
- Personnel issues › Action/decision › Action › Forgotten action/omission › Maintenance personnel
Pilot
- Certificate: airline transport pilot, commercial pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 1,716.4 hours in all; 58.2 in this make and model; 102.3 in the last 90 days; 36.8 in the last 30 days; 1,623.8 as pilot in command
- Last flight review: September 4, 2024
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: left
- Injury: minor injuries
The aircraft
- Airframe total time: 4,711.3 hours
- Last inspection: annual inspection, August 22, 2024; 0.1 hours since
- Maximum gross weight: 2,300 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-320-D2G (piston); 0 hours total
The flight
- Flight plan: none
- Runway 5, 5,852 ft by 100 ft
Weather at the time
- Light: daylight
- Wind: from 040° at 6 knots
- Visibility: 7 statute miles
- Sky: scat at 4,900 ft
- Temperature: 86°F (30°C), dew point 61°F (16°C)
- Altimeter: 29.90 inHg
- Observation at 3:35 pm from SPA, 1 miles away
Weather report (METAR): KSPA 201935Z AUTO 04006KT 7SM SCT049 SCT065 30/16 A2990 RMK AO2
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Photographs from the investigation 3 pictures from the NTSB's docket, as the NTSB released them
Photograph 1 – Deformation noted to rudder and vertical stabilizer
Photograph 2 – Deformation and skin separation noted to right wing
Photograph 3 – Buckling noted to fuselageThe 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
10 documents, released by the NTSB on August 19, 2026. 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.
| # | Document | What it is | |
|---|---|---|---|
| 1 | NTSB 6120 1 Form | PDF, 9 pages | View Download |
| 2 | Mor Mechanic Statement | PDF, 1 page | View Download |
| 3 | Mor Divco Checklist | PDF, 1 page | View Download |
| 4 | Lycoming Overhaul Manual Excerpts | PDF, 4 pages | View Download |
| 5 | Maintenance Records | PDF, 12 pages | View Download |
| 6 | Photo Array | PDF, 4 pages · our copy | View Download |
| 7 | Examination Summary | PDF, 7 pages | View Download |
| 8 | Mor NTSB Materials Laboratory Report | PDF, 2 pages | View Download |
| 9 | Statement of Party Representatives to NTSB Investigation | PDF, 14 pages | View Download |
| 10 | Wreckage Release Form | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N7037G on the register today · the tail number may have moved to another aircraft since
- Cessna 172 Skyhawk 20,692 registered today · the model family and its accident history
- Cessna 72,677 aircraft on the register
- Engine: Lycoming O-320-D2G 21 aircraft carry this series today · as the NTSB recorded it
- Spartanburg Downtown Meml/Simpson Field · nearest airport
- Accidents and incidents in South Carolina 1,036 since 1982 · 173 in the last ten years
- South Carolina 3,115 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ERA24LA388.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.
