FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA11FA133 · Potez-Air Fouga CM 170 MAGISTER

2 Feb 2011 · Kissimmee, FL, United States

Potez-Air Fouga CM 170 MAGISTER · Accident: aerodynamic stall/spin on approach

From Kissimmee Gateway Airport (ISM) to Kissimmee Gateway Airport (ISM)

Report a problem

Event

NTSB case
ERA11FA133
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
2 · 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

Potez-Air Fouga CM 170 MAGISTER

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
N415FM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Kissimmee Gateway Airport (ISM), Kissimmee, FLTo Kissimmee Gateway Airport (ISM), Kissimmee, 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
Approach
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
Aerodynamic stall/spin
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

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

NTSB narrative

After the repair of a number of hydraulic leaks, a post-maintenance check flight was conducted from the vintage jet trainer's home airport with a visiting pilot/mechanic and the pilot/owner onboard. After the airplane took off, it departed the airport traffic pattern for in-flight tests. About 11 minutes later, the airplane reentered the airport traffic pattern and completed a left, overhead, mid-field break about 600 feet above ground level (agl). A voice recognized as the pilot/mechanic's then advised the tower that the three landing gear were down and locked, and the airplane arrived at the abeam position about 500 feet agl and 215 knots. The airplane then eased out of the turn and briefly flew a straight course that angled toward the runway before commencing a sharp turn toward the runway with an observed 90-degree angle of bank. The airplane was then seen descending rapidly before pitching up, overshooting the extended runway centerline, nosing down, and impacting the ground. Both pilots were ejected when the airplane impacted the ground, and neither of the destroyed cockpits nor an airport security video could provide definitive evidence as to which pilot was in which seat. However, because the pilot/mechanic’s voice was on all radio transmissions, including a transmission that he was unfamiliar with the airport, it is likely that he was in the front seat and flying the airplane.

Wreckage examination revealed that the airplane had impacted the ground in an approximately 45-degree left angle of bank, about 5 degrees nose-low. The landing gear were down and the push button selectors were in the "normal" position, indicating that landing gear were extended normally. The two left-wing flap segments were separated from the extensively damaged wing, and the differing cockpit wing flap indicators were unreliable due to cockpit and airplane damage. However, the two relatively intact right-wing flap segments were up and flush with the wing, consistent with the flaps being up at impact. The emergency airbrake selector was in the "out" position, indicating that the pilot/mechanic had recognized a loss of hydraulic pressure after lowering the landing gear, but before he could effectively deploy airbrakes or flaps. There are no means to lower flaps following a loss of hydraulic pressure. The pilot/mechanic should have extended the downwind leg for a flaps-up approach, per the abnormal procedures. However, he continued the high angle-of-bank, as-configured approach, but did not maintain sufficient airspeed to preclude an "accelerated maneuver stall."

Probable cause

The pilot/mechanic's improper decision to continue a tight-turning landing pattern after a loss of hydraulic pressure, and his subsequent failure to maintain adequate airspeed during that pattern, which resulted in an accelerated maneuver stall. Contributing to the accident was a loss of hydraulic pressure after the extension of the landing gear.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA11FA133
Event ID
20110202X85818
Case number
ERA11FA133
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: 540db6724df6c5cb47e3f08e3e2c254a7d775ed849b47eaceb418b5078218de9; retrieved 2026-09-13T21:13:31.458Z.