FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA25LA301 · Cessna 560XL

14 Aug 2025 · Oakland Park, FL, United States

Alliance Aviation Group Cessna 560XL · Accident: flight control system malfunction/failure during initial climb

From Fort Lauderdale Executive Airport (FXE) to Orlando Executive Airport (ORL)

Report a problem

Event

NTSB case
ERA25LA301
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
Ongoing
Event fatalities
Unknown
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

Cessna 560XL

Aircraft type
Cessna 560
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
N802TD
Onboard fatalities
Unknown
Route
From Fort Lauderdale Executive Airport (FXE), Fort Lauderdale, FLTo Orlando Executive Airport (ORL), Orlando, FL
Aircraft age
About 24 years (built 2001)
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
Initial climb
Defining eventThe 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
Flight control system malfunction/failure
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

No findings designated as a cause are recorded in the NTSB data yet.

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

NTSB narrative

On August 14, 2025, about 1715 eastern daylight time, a Cessna 560XL, N802TD, was substantially damaged when it was involved in an accident near Oakland Park, Florida. The airline transport pilot and commercial pilot were not injured. The airplane was operated as a Title 14?Code of Federal Regulations Part 91 business flight.

The pilot and the commercial pilot arrived at Fort Lauderdale Executive Airport (KFXE), Fort Lauderdale, Florida, about 1100, with the intent to fly the airplane to Orlando Executive Airport (ORL), Orlando, Florida, with an estimated departure time of 1400. The airplane was at FXE to be painted; however, shop personnel informed them upon their arrival that the airplane was not ready to be released, and their 1400 departure time would have to be pushed back. The pilot said he utilized this time to perform a quick walk around the airplane, he adjusted the seat and rudder pedals and made plans to do a final operational check once the airplane was towed to a different location on the airport to be fueled.

The pilot said that when the airplane was ready, he performed an external pre-flight check of the airplane and arranged to add 3,500 pounds of fuel. Personnel from the paint shop arrived at the airplane, and he and the commercial pilot assisted them with multiple operational checks which included engine runs, manipulation of the control column to check flight control positioning, and cycling of the flaps from 0 to 35 degrees (five cycles). During this time, the pilot noticed that the control column seemed a bit closer than he remembered when it was full forward as compared to a different airplane of the same make and model. Otherwise, the controls seemed to move as normal with no unusual binding or limitations.

The pilot said that he and the commercial pilot completed normal pre-engine start checks, started the engines and taxied to the active runway, held short, then taxied onto the runway after receiving takeoff clearance. After taxiing onto the runway, the pilot gave the controls to the commercial pilot. The pilot said the takeoff roll was uneventful but once he retracted the landing gear, he noticed that the airplane was at an unusually high pitch and requested that the commercial pilot to lower the nose. He said, it became immediately obvious that she was unable to do this, so he assumed command of the airplane and placed full available forward pressure on the control column. An emergency was declared and a 180° left turn was made in an attempt to return, but both pilots were unable to arrest the climb, climbing to 9,500 ft, which was well above their assigned altitude of 2000 ft mean sea level. The tower controller asked them if they could see the runway and we were unable to see it due to the uncommanded steep climb. The tower controller then asked them to change to a Miami Air Route Traffic Control Center frequency, but he and the commercial pilot had both arms pressing forward on the control column in an attempt to prevent a stall.

Over the next several minutes, the crew attempted to maintain control of the airplane during a series of radical pitch up events into one or more stalls followed by an uncommaded steep pitch down event. The flight then proceeded towards Fort Lauderdale/Hollywood International Airport for landing on runway 10L, where the pilot performed a 360° turn to reduce airspeed. With the throttles at idle power and the speed brakes deployed, he was able to lose about 120 kts of airspeed in the 360° turn but was still about 30 knots above normal approach speed. The pilot continued towards the runway and when in ground effect, the airplane pitched up again uncommanded. The pilot was able to correct that condition and landed on the last 1/4 of the runway before he brought the airplane to a full stop. The pilots then taxied the airplane after receiving approval from emergency personnel.

Postaccident examination of the airplane revealed an elevator pushrod was bent with evidence of contact with an adjacent structural member.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record ERA25LA301
Event ID
20250815200796
Case number
ERA25LA301
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: b3839e13cec4fc3bcb7e6f978da0240c30d494ca156b5b4b2910c5bada21f9a9; retrieved 2026-09-16T20:13:17.928Z.