FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA25FA120 · Rockwell 112 UNDESIGNAT

15 Feb 2025 · Covington, GA, United States

Rockwell 112 UNDESIGNAT · Accident: course deviation during takeoff

From an unrecorded airport to Valdosta Regional Airport (VLD)

Report a problem

Event

NTSB case
ERA25FA120
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Ongoing
API-reported fatalities
2 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Rockwell 112 UNDESIGNAT

Aircraft type
Rockwell 112
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N1423J
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo Valdosta Regional Airport (VLD), Valdosta, GA
Aircraft age
About 50 years (built 1975)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Takeoff
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Course deviation
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

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.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record ERA25FA120
Event ID
20250216199706
Case number
ERA25FA120
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2025-02-16.
  • API snapshot SHA-256: 73135be39509aad2f93e8bfcab10849ec04fdba41acf549dc8a1ae3f8d095896; retrieved 2026-09-15T09:02:24.599Z.