FTW83FA222 · Cessna 170B
Cessna 170B · Accident: in flight collision with terrain/water while maneuvering
From an unrecorded airport to E02 · TX
Event
- NTSB case
- FTW83FA222
- 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
- 0
- 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
Cessna 170B
- Aircraft type
- Cessna 170
- 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
- N3038A
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo E02 · 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
- Maneuvering
- 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
- In flight collision with terrain/water
- 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 › Clearance, not maintained
- Pilot in command › Judgment, poor
- Pilot in command › Proper altitude, not selected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
ACCORDING TO A TRUCK DRIVER, HE WAS PROCEEDING NORTHBOUND ON A HIGHWAY, WHEN HE SAW THE AIRCRAFT ENTER WHAT HE DESCRIBED AS A LOOP FROM APRX 100 FT AGL. THE WITNESS THEN LOST SIGHT OF THE ACFT, BUT SHORTLY AFTER THAT, HE SAW A LARGE EXPLOSION ON THE GROUND WHERE THE ACFT CRASHED & BURNED. RECENTLY, THE PLT HAD BEEN OBSERVED PERFORMING CHANDELLES & LAZY EIGHTS AT LOW ALT. ALSO, HE HAD RECENTLY DISCUSSED THE POSSIBILITY OF LOOPING THE ACFT & WAS ADVISED NOT TO. AN EXAM OF THE WRECKAGE REVEALED THAT THE ACFT HAD IMPACTED IN A 20 TO 30 DEG NOSE DOWN, WINGS LEVEL ATTITUDE. NO EVIDENCE OF A PREIMPACT, MECHANICAL FAILURE OR MALFUNCTION WAS FOUND. THE PLT HAD NOT RECEIVED FORMAL TRAINING IN AEROBATICS. THE ACFT WAS CERTIFIED FOR UTILITY CATEGORY OF FLT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record FTW83FA222
- Event ID
- 20001214X42967
- Case number
- FTW83FA222
- 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. 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: 82f02f45d293c104b3d32084d212c5cf501bb4e9a74a89cee66a2a5d4bef27ee; retrieved 2026-09-21T06:50:48.287Z.