ATL83LA087 · Lockheed 18-56
Lockheed 18-56 · Accident: loss of control on ground/water during takeoff
From an unrecorded airport to Miami International Airport (MIA)
Event
- NTSB case
- ATL83LA087
- 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
Lockheed 18-56
- Aircraft type
- Lockheed 18
- 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
- N520R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Miami International Airport (MIA), Miami, 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 91F: Special Flt Ops.
- 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
- Loss of control on ground/water
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall/mush
- 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 › Parking brakes, inadvertent use
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT REPORTED THAT AFTER HE TAXIED TO THE RWY, THE #1 OIL TEMP WAS NOT UP TO THE MINIMUM TEMP. HE SET THE PARKING & ADVANCED THE #1 THROTTLE TO 1500 RPM UNTIL THE ENGINE WARMED UP. WHEN BOTH OIL TEMPS WERE WITHIN LIMITS, HE ADVANCED BOTH THROTTLES TO 30 INCHES MP & 2250 RPM FOR A PRETAKEOFF CHECK. AT THAT TIME, HE USED THE NORMAL (TOE) BRAKES, SINCE THE PARKING BRAKE WOULD NOT HOLD THE ACFT ABOVE APRX 1700 RPM. HE THEN APPLIED FULL POWER & RELEASED THE BRAKES FOR TAKEOFF. AS HE STARTED TO ROLL WITH A SLIGHT LEFT X-WIND, THE ACFT BEGAN DRIFTING LEFT. HE CORRECTED WITH RIGHT RUDDER, SOME RIGHT BRAKE & RIGHT AILERON. THE ACFT THEN BEGAN DRIFTING RIGHT & THE PLT SUSPECTED A WIND-SHIFT FROMTHAT DIRECTION. HE APPLIED LEFT RUDDER & RIGHT AILERON, BUT THE PLANE VEER RIGHT, WENT OFF THE RWY & HEADED FOR A DITCH.UNABLE TO STOP, THE PLT TRIED TO CLEAR THE DITCH. AS THE ACFT BECAME AIRBORNE, THE LEFT WING DROPPED & HIT THE GROUND, AND THE ACFT YAWED & CRASHED. THE PARKING BRAKE WAS FOUND PARTIALLY ENGAGED. TIRE MARKS WERE EVIDENT ON THE RWY.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL83LA087
- Event ID
- 20001214X41929
- Case number
- ATL83LA087
- 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: b19f816d68131fcb058891731d65b765d249fb456268ae68e30ded0c0c0149cf; retrieved 2026-09-23T23:30:05.530Z.