ATL89LA029 · Cessna 172N
Tri-City Aviation Cessna 172N · Accident: on ground/water collision with object during landing
From Bristol, TN to an unrecorded destination
Event
- NTSB case
- ATL89LA029
- 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
- 0 · 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 172N
- Aircraft type
- Cessna 172
- 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
- N734ZM
- Operator
- Tri-City Aviation
- Onboard fatalities
- Unknown
- Route
- From Bristol, TNTo not recorded
- 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
- Landing · landing roll
- 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
- On ground/water collision with object
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Brakes(normal), improper use of
- Pilot in command › In-flight planning/decision, improper
- Pilot in command › Unsuitable terrain or takeoff/landing/taxi area, selected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT REPORTED THAT HE WAS FERRYING THE AIRPLANE TO OBTAIN SCHEDULED MAINTENANCE. UPON ARRIVAL OVER THE ARPT, HE FOUND THAT THE ONLY RWY WAS CLOSED FOR MAINTENANCE. HE THEN ELECTED TO LAND ON A TAXIWAY. HE MADE A SHORT-FIELD LDG AND APPLIED THE BRAKES 'FIRMLY' AFTER TOUCHDOWN. BOTH TIRES BLEW OUT DURING THE LDG ROLL, AND HE LOST CONTROL OF THE ACFT. THE ACFT COLLIDED W/ A PARKED TRUCK AND A FENCE. EXAM OF THE ACFT TIRES REVEALED THAT THEY HAD BLOWN OUT AS A RESULT OF EXCESSIVE BRAKING. THE DISTANCE FROM THE TAXIWAY ENTRANCE AT THE RWY EDGE TO THE TRUCK WAS APPROXIMATELY 500 FT. SEVERAL HANGARS & OTHER OBSTACLES WERE LOCATED OFF THE END OF THE TAXIWAY ALONG THE ACFT'S INITIAL DIRECTION OF TRAVEL. EXAM OF A CESSNA 172N INFO MANUAL REVEALED THAT ABOUT 500 FT WAS REQUIRED FOR THE LDG ROLL GIVEN THE CONDITIONS REPORTED BY THE PLT. A NOTAM (D) WHICH ADVISED OF THE CLOSED RWY WAS ISSUED 2 DAYS EARLIER, AND WAS IN EFFECT AT THE TIME OF THE ACCIDENT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL89LA029
- Event ID
- 20001213X27193
- Case number
- ATL89LA029
- 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: a3187c17402a3ca170d9ffcce0a11248afb88011f3f59a8eeb074e456058cbbc; retrieved 2026-09-23T08:28:43.252Z.