FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW02LA127 · Piper PA-32R-301T

23 Apr 2002 · Bogalusa, LA, United States

Piper PA-32R-301T · Accident: on ground/water collision with object during takeoff

From George R Carr Memorial Air Field (BXA) to George R Carr Memorial Air Field (BXA)

Report a problem

Event

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

Piper PA-32R-301T

Aircraft type
Piper PA-32
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
N8108V
Operator
Unknown
Onboard fatalities
Unknown
Route
From George R Carr Memorial Air Field (BXA), Bogalusa, LATo George R Carr Memorial Air Field (BXA)
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
Takeoff · roll/run
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

  • Object › Animal(s)

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 pre-flight inspection, the pilot taxied the airplane to runway 36. During the takeoff roll at 70 knots, the pilot began rotation. At 75 knots, the nose wheel lifted off the runway, and from the west, a deer crossed in front of the airplane. The airplane's left wing struck the deer, and the pilot aborted the takeoff. The pilot then taxied the airplane back to the flight line. The airport did not have a perimeter fence around it that would prevent deer from entering the runway environment.

Probable cause

a deer that ran in front of the airplane during the takeoff phase. A contributing factor was the lack of an airport perimeter fence to prevent deer from entering the runway environment.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW02LA127
Event ID
20020423X00573
Case number
FTW02LA127
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: 3259b86444f89d101a2cbab4d801a0f50c5017be7f0bf02450e980383519ae00; retrieved 2026-09-22T10:59:16.793Z.