ATL82DA206 · Pitts S2S
Pitts S2S · Accident: on ground/water collision with object during landing
From Arlington, TN to Santa Fe Municipal Airport (SAF)
Event
- NTSB case
- ATL82DA206
- 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
Pitts S2S
- Aircraft type
- Pitts S2
- 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
- N31461
- Operator
- Howard M. Mullins · private individual
- Onboard fatalities
- Unknown
- Route
- From Arlington, TNTo Santa Fe Municipal Airport (SAF), Santa Fe, NM
- 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
- Airport personnel › Unsafe/hazardous condition warning, inadequate
Approximate · Estimated position: the centre of Somerville, TN, the place the record names. Not the accident site.
NTSB narrative
SHORTLY AFTER TOUCHDOWN DURING A FORMATION LANDING, THE WINGMAN'S AIRCRAFT STRUCK AN ENGINE STAND THAT HAD BEEN PLACED OVER A HOLE IN THE RUNWAY. THE HOLE WAS LOCATED ABOUT 900 FT FROM THE APPROACH END AND WAS ABOUT 2 FT LONG, 1 FT WIDE, AND 1 FT DEEP. IT WAS MADE WHEN THE NOSEWHEEL OF A SABRELINER HAD BROKEN THROUGH THE ASPHALT ON THE PREVIOUS DAY. FLIGHT SERVICE WAS NOTIFIED THAT THE RUNWAY WAS CLOSED AND A NOTAM WAS ISSUED, BUT THE PILOT STATED THAT THE FSS HAD NOT RECEIVED IT UNTIL AFTER THE OCCURRENCE. THE MEMPHIS FAA AIRPORTS DISTRICT OFFICE HAD INSTRUCTED THAT THE AIRPORT BE MARKED CLOSED WITH AN "X" ACROSS THE ENDS OF THE RUNWAY. THE PILOT STATED THAT THERE WERE NO CLOSED MARKINGS PLACED ON THE RUNWAYS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL82DA206
- Event ID
- 20020917X02785
- Case number
- ATL82DA206
- 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: 7a51149c9f4521d8b72a029d7dc4ce0132f54ab14dfc8ca63cdc57706dcb4c3c; retrieved 2026-09-24T02:11:21.867Z.