The U.S. aircraft register, updated daily
Accidents · NTSB ERA25FA120 · Preliminary: the investigation is not finished

Rockwell 112 accident near Covington, Georgia, February 16, 2025

On February 16, 2025 at about 4:00 am local time, a 1975 Rockwell 112, registered N1423J, was destroyed in an accident during takeoff near Covington, Georgia (Covington Municipal airport). It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.

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

What the record shows

Date
February 16, 2025 · about 4:00 am local time
Place
Covington, Georgia · Covington Municipal · map
Type
Accident
Injuries
2 people were killed.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Rockwell 112 UNDESIGNAT, built 1975
Registration
N1423J · registry record · serial 423
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

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

On February 15, 2025, about 2300, a Rockwell 112, N1423J, was destroyed when it was involved in an accident near Covington, Georgia. The private pilot and one passenger were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to Federal Aviation Administration (FAA) air traffic control radio communication information, the pilot contacted Atlanta Terminal Radar Approach Control (TRACON) Departure Radar North (DRN) position for an instrument flight rules (IFR) clearance and release from Covington Municipal Airport to Valdosta Regional Airport, Valdosta, Georgia. At 2256, the pilot advised the controller he would be departing from runway 10 and was ready to depart. The DRN controller issued the clearance with an initial climb to 3,000 ft, as well as a departure frequency and transponder code, which the pilot correctly read back. The pilot was advised that the release for departure clearance was void if he had not departed within 10 minutes, which he acknowledged. There was no record that the pilot contacted the DRN controller after his last audio communication while on the ground. A review of airport security cameras revealed that a light from the airplane came into view during the takeoff roll on runway 10 at 2259 and went out of view from that camera several seconds later. The airplane at the time when it went out of view was located about 1,800 ft down the runway. Another airport security camera with a view of where the airplane impacted trees and terrain recorded a very bright light filling the upper portion of the screen at about 1 minute later. According to the Covington-Newton County Communications Center Call Detail Report, at 2303, a mobile phone belonging to the passenger dialed 911 and advised by automated voice message that the owner was in a severe crash and was not responding to their phone. The coordinates of the location that were given were about 34 ft northeast of the actual resting position of the main wreckage. Additionally, the Covington Police Department dispatch received a call from the FAA TRACON about 2322 reporting that the accident airplane was supposed to depart at 2259 and they had not heard from the pilot yet. Law enforcement personnel responded to the airport and when they were at the north side of the airport from behind two chain link fences officers noted a fire erupting from a wooded area. The officers cut access points in both chain link fences, responded to the site with handheld fire extinguishers and attempted to extinguish the fire. The accident site was located about 4,230 ft down and 620 ft north of the northern edge of runway 10. The cockpit and cabin were consumed by the postimpact fire. The wreckage was recovered and retained for further examination.

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. Course deviation during takeoff defining event
  2. Collision with terrain or object (not controlled flight into terrain) during takeoff
  3. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
  4. Fire/smoke (post-impact) during post (impact)

The aircraft

  • Airframe total time: 2,550 hours
  • Last inspection: annual inspection, November 22, 2024
  • Maximum gross weight: 2,550 lb
  • Seats: 4
  • Landing gear: retractable
  • Fire on the ground

The flight

  • Destination: VLD Valdosta GA
  • Flight plan: IFR
  • Runway 10, 6,000 ft by 100 ft
  • A second pilot was aboard

Weather at the time

  • Light: night
  • Wind: from 090° at 4 knots
  • Visibility: 0.5 statute miles
  • Sky: overcast at 200 ft
  • Temperature: 48°F (9°C), dew point 48°F (9°C)
  • Altimeter: 29.85 inHg
  • Observation at 10:55 pm from KCVC

Weather report (METAR): KCVC 160355Z AUTO 09004KT 1/2SM -DZ BR OVC002 09/09 A2985 RMK AO2

Injuries

FatalSeriousMinorNone
Flight crew2

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

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

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

1983-09-13ATL83LA367 · accident near Batesburg, SC · substantial damage · no injuries

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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.