FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL00LA093 · Piper PA-28-235

26 Sept 2000 · Adel, GA, United States

Piper PA-28-235 · Accident: on ground/water collision with object during landing

From Taylor County Airport (AAS) to Lakeland Linder International Airport (LAL)

Report a problem

Event

NTSB case
ATL00LA093
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

Piper PA-28-235

Aircraft type
Piper PA-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
N33735
Operator
Robert J. Luckhurst · private individual
Onboard fatalities
Unknown
Route
From Taylor County Airport (AAS), Campbellsville, KYTo Lakeland Linder International Airport (LAL), Lakeland, FL
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 › Wrong runway, selected

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

According to the pilot, the airplane was low on fuel and he elected to divert into Adel, Georgia. Due to concerns about the fuel status, the pilot elected to land straight-in on runway 15. Runway 5 was the active runway, and runway 15 was marked closed. During the landing roll, the airplane collided with a wood block. During the examination of the airplane, all fuel tanks were found intact, and fuel was found in all four fuel tanks. No mechanical malfunctions were found during the engine examination of the airplane.

Probable cause

The pilot's selection of a closed runway for landing. Contributing factors were his inadequate inflight planning/decision and the wood block on the runway..

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL00LA093
Event ID
20001212X21910
Case number
ATL00LA093
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: eca38490a824521d1ed88082e52d719ca6a906b18c964df28cdc7b69c6c7d31c; retrieved 2026-09-22T12:25:14.005Z.