FTW02FA112 · North American T-28B
North American T-28B · Accident: loss of control in flight during initial climb
From Garner Field (UVA) to Garner Field (UVA)
Event
- NTSB case
- FTW02FA112
- 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
- Completed
- API-reported fatalities
- 1 · 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
- Visual Meteorological Cond
North American T-28B
- Aircraft type
- North American T-28
- 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
- N13RW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Garner Field (UVA), Uvalde, TXTo Garner Field (UVA), Uvalde, TX
- Aircraft age
- Not recorded
- 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
- Initial climb
- First occurrenceThe 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
- Loss of control in flight
- 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
- Pilot in command › Aircraft control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
After a normal ground run-up and take off, the vintage T-28B airplane, flown by a 3,500-hour airline tranport rated pilot, impacted terrain following a loss of control after performing a downwind departure and climbing to an altitude of 800-1,000 feet agl. Several witnesses who observed takeoff sequence did not notice any abnormalities or abnormal sounds from the aircraft. One of the witnesses reported that the aircraft made a left turn with a "normal" climb out to downwind, and that the engine sounded normal. The aircraft appeared "stable" in the climb and was parallel to the runway approximately 800-1,000 feet above ground level (agl) on the downwind departure. The aircraft then entered a left turn, and just as the turn was completed, the aircraft "did one to one and one-half barrel rolls in level flight." Then, while inverted, the aircraft "tucked under and went straight down." Another witness reported that as the aircraft turned, the aircraft "rolled over and flew inverted for about two seconds," then "flew nose first into the ground." No radio transmissions or distress calls were received from the accident aircraft. Logbooks for the aircraft were not recovered. Prior to the accident, the aircraft had been stored in a hangar that was operated by a aviation museum on airport property, and had not been flown for several months prior to the morning of the accident. According to a family member and airport personnel, access to the hangar was not controlled, and that the general public could come in to look at the aircraft. The wreckage debris was severely fragmented and was distributed over an area approximately 110 feet long and 75 feet wide, in a general north-to-south orientation. Evidence of an extensive ground fire was observed surrounding the debris, and mostly all of the wreckage debris was found within the boundaries of the fire area. The main portion of the wreckage, which included the engine, propeller, both wings, and fractured fuselage structure was found in a shallow crater in the southern-most area of the scattered debris. The orientation of the engine and forward section of the fuselage within the crater exhibited evidence that the aircraft impacted the ground in a nose-low, inverted attitude. The 3-blade propeller exhibited evidence of rotation at the time of impact. Mostly all of the wreckage within and adjacent to the impact point was consumed by post-impact fire. Due to the extensive impact and fire damage, flight control continuity could not be established from the cockpit outboard to the wings, however, flight control cables and push/pull rods that were observed appeared to be damaged as a result of impact. Flight control cables, rods, and bell cranks within the empennage rearward to the horizontal stabilizer, elevators, and rudder did not reveal pre-impact anomalies. Several pieces of flight control surfaces, flaps, and wing skin material were found north of the impact crater, and appeared to have been "blown back" during the impact sequence. The landing gear was found in the retracted position. Examination of the wreckage did not reveal any pre-impact anomalies.
Probable cause
The pilot's failure to maintain control of the aircraft for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW02FA112
- Event ID
- 20020411X00498
- Case number
- FTW02FA112
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: f5385e1722fc8d0b1d1a53849c44c0641399adfb97ff6c79a3f6564ac23cc06e; retrieved 2026-09-20T20:07:15.535Z.