FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL84LA032 · Piper PA-61P

29 Oct 1983 · Norfolk, VA, United States

Piper PA-61P · Accident: overrun during takeoff

From Norfolk International Airport (ORF) to PBI · West Palm Beach, FL

Report a problem

Event

NTSB case
ATL84LA032
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-61P

Aircraft type
Piper PA-61
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
N9531Q
Operator
Unknown
Onboard fatalities
Unknown
Route
From Norfolk International Airport (ORF), Norfolk, VATo PBI · West Palm Beach, 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
Takeoff
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
Overrun
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 › Aborted takeoff, delayed
  • Pilot in command › Performance data, not understood

Approximate · Estimated position: the centre of Norfolk, VA, the place the record names. Not the accident site.

NTSB narrative

THE PLT STATED THAT DURING THE TAKEOFF ROLL THE AIRSPEED HAD ACCELERATED THROUGH 128 KTS, BUT AS THE TAKEOFF CONTINUED THE AIRSPEED DROPPED TO 115 KTS & REMAINED BETWEEN 100-115 KTS. AFTER ROTATION THE ACFT WOULD NOT CLIMB OR ACCELERATE ABOVE 100-115 KTS. THE PLT RECHECKED THE POWER PLANT CONTROLS & ACFT SYSTEMS OPERATIONS. THE ACFT WOULD ONLY CLIMB TO ABOUT 20 FT AGL. THE PLT ELECTED TO ABORT THE TAKEOFF WITH ABOUT 1200 FT OF RUNWAY REMAINING. THE ACFT TOUCHED DOWN & THE PLT APPLIED MAXIMUM BRAKING, BUT THE ACFT RAN OFF THE END OF THE RWY COLLAPSING THE LANDING GEAR. THE PLT REPORTED APPLYING RIGHT RUDDER TO MAINTAIN DIRECTIONAL CONTROL DURING THE ATTEMPTED CLIMBOUT, BUT NO MALFUNCTION OF THE LEFT ENG WAS FOUND. ACCORDING TO THE OWNER'S MANUAL THE ACCELERATE STOP DISTANCE WAS AMPLE.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record ATL84LA032
Event ID
20001214X44757
Case number
ATL84LA032
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: 4de4abcb05a62e09b539bbf5f753fc80e2adbbd62d3ffd257ca1b88f5b58cb3b; retrieved 2026-09-23T21:09:53.358Z.