Cessna 172P accident near Winder, Georgia, March 25, 2022
On March 25, 2022 at about 2:48 pm local time, a 1981 Cessna 172P, registered N62283, was destroyed in an accident during approach (VFR pattern final) near Winder, Georgia (Barrow County airport). It was an instructional flight under general aviation rules (Part 91). 1 person was seriously injured and 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 detect the damaged aileron cable during the most recent inspections, which resulted in the separation of the aileron control cable and subsequent loss of airplane control.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 25, 2022 · about 2:48 pm local time · cases in 2022
- Place
- Winder, Georgia · Barrow County · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person was seriously injured and 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172P, built 1981 · all 172Ps on the register
- Registration
- N62283 · registry record · serial 17275244
- Damage
- Destroyed
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The flight instructor and student pilot completed several touch-and-go landings and on the final circuit in the traffic pattern, while on the final approach, the student pilot turned the yoke, and felt a sensation like the aileron cable disconnecting. The flight instructor took control of the airplane and noted that he could turn the control yoke 360° without a response from the airplane. Having no aileron control, the airplane veered to the right and descended into trees. A post-impact fire ensued that destroyed the airplane. Examination of the wreckage revealed that there was a break in the aileron control cable system near the right control column. A metallurgical examination of the break in the aileron control cable revealed that the mating fracture surfaces exhibited a flattened area over more than half the cable cross-section, with the remainder of the wires exhibiting features consistent with overstress fractures. The wires in the flattened area exhibited consistent, parallel streaks and witness marks. These marks may indicate wear from rubbing against an adjacent component in this area or they may be consistent with some partial cutting operation. If rubbing of the cable was creating wear, this process would have removed material wire-by-wire, and strand-by-strand over time. The remaining wires would have fractured from tensile overstress when there were no longer enough intact wires to carry the stress. It’s likely the overstress fracture occurred during the final leg of the traffic pattern, which was consistent with reports from the pilot and flight instructor that the flight controls no longer functioned properly during the final landing approach. According to maintenance records, the airplane was inspected, in accordance with the maintenance manual and Part 43 appendix D, 9 times during the 13 months before the accident. According to both inspection checklists, the aileron control cable should have been inspected and found unairworthy at some point due to its condition. Therefore, it’s likely maintenance personnel overlooked the damaged aileron control cable during the most recent inspections.
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
- Flight control sys malf/fail during approach (VFR pattern final) defining event
- Loss of control in flight during approach (VFR pattern final)
The NTSB's findings
- Aircraft › Aircraft systems › Flight control system › Aileron control system › Inadequate inspection other cases naming the flight controls
- Aircraft › Aircraft systems › Flight control system › Aileron control system › Fatigue/wear/corrosion other cases naming the flight controls
- Personnel issues › Task performance › Inspection › Scheduled/routine inspection › Maintenance personnel
Flight instructor
- Certificate: flight instructor, commercial pilot
- Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
- Last flight review: August 30, 2021
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: rgt
- Injury: serious injuries
Dual student
- Certificate: student
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: left
- Injury: minor injuries
The aircraft
- Airframe total time: 24,830 hours
- Last inspection: 100-hour inspection, March 15, 2022; 14 hours since
- Maximum gross weight: 2,400 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-320-D2J (piston); 0 hours total
- Fire on the ground
- Operator: Flight School of Gwinnett INC
The flight
- Flight plan: none
- Runway 31, 5,202 ft by 100 ft
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: from 310° at 11 knots, gusting 19
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 59°F (15°C), dew point 32°F (0°C)
- Altimeter: 29.92 inHg
- Observation at 10:55 am from WDR, 1 miles away
Weather report (METAR): KWDR 251455Z AUTO 31011G19KT 10SM CLR 15/00 A2992 RMK AO2
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | 1 |
Photographs from the investigation 4 pictures from the NTSB's docket, as the NTSB released them
Photo 1 – Accident Site (FAA Photo)
Photo 2 – Accident Site (FAA Photo)
Photo 3 – Engine (FAA Photo)
Photo 4 – Engine (FAA Photo)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
9 documents, released by the NTSB on September 27, 2023. 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 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | Student Pilot's Statement | PDF, 2 pages | View Download |
| 3 | Photographs | PDF, 4 pages · our copy | View Download |
| 4 | Memorandum for Record - Wreckage Examination Summary | PDF, 2 pages | View Download |
| 5 | Materials Laboratory Factual Report | PDF, 16 pages | View Download |
| 6 | Cessna 172 Maintenance Manual Excerpt | PDF, 8 pages | View Download |
| 7 | Airframe Maintenance Log Excerpts | PDF, 6 pages | View Download |
| 8 | Part 43 Appendix D | PDF, 3 pages | View Download |
| 9 | Evidence Control Form | PDF, 3 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Other NTSB records under N62283 the same tail number, which may have belonged to a different aircraft at the time
Connections how this case links to the rest of the register
- N62283 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-D2J 96 aircraft carry this series today · as the NTSB recorded it
- Barrow County · nearest airport
- Accidents and incidents in Georgia 2,138 since 1982 · 360 in the last ten years
- Georgia 8,801 aircraft registered
- Other NTSB records under N62283 1 records · the number may have belonged to another aircraft at the time
The whole map of how records connect · these connections as data: /graph/accident/ERA22LA167.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.
