FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

IAD03MA049 · Sino-Swearingen SJ30-2

26 Apr 2003 · Loma Alta, TX, United States

Sino-Swearingen SJ30-2 · Accident: loss of control in flight en route

From San Antonio International Airport (SAT) to an unrecorded destination

Report a problem

Event

NTSB case
IAD03MA049
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
1 · 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

Sino-Swearingen SJ30-2

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
N138BF
Operator
Unknown
Onboard fatalities
Unknown
Route
From San Antonio International Airport (SAT), San Antonio, TXTo not recorded
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
En route · descent
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 in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Manufacturer › Inadeq substantiation process, inadeq documentation

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The corporate jet was in a descent to attain a Mach 0.884 target speed during an airplane type certification flutter test. The airplane (a unique test bed) had a known speed-dependent tendency to roll right which was attributed to wing and aileron twist deviations. As the speed increased during the accident flight, the pilot had to apply full left aileron to be able to maintain airplane control. The airplane completed the test point about 30-degrees right-wing-low, and subsequently began to roll to the right, "like a barrel roll...not real fast," that the pilot reported he could not stop. Although the manufacturer’s engineering analysis (which did not include any high-speed wind tunnel testing) predicted positive lateral stability up to Mach 0.90, lateral control was lost during the accident flight, and the airplane rolled about 7 times during a 49-second timeframe, from about 30,500 feet until a near-vertical ground impact. A review of telemetry data revealed that, just before the rolls began, the airplane's elevator moved to the 3.5 degrees trailing-edge-up (TEU) position, and the airplane's heading deviated right. Less than 1 second later, the rudder moved from 2 degrees trailing-edge-left (TEL), to 6.5 degrees TEL, and the combination of the TEU elevator and the left rudder input coincided with a marked increase in airplane's right deviation. Elevator-up deflection and rudder-left defection were maintained, with some variation in magnitude, to nearly the end of the data. Because the known speed-dependent tendency to roll right had created significant control problems on a previous flight, the ailerons were removed, modified and replaced, and a Gurney flap was added to the right wing. After the addition of the Gurney flap, the lateral trim margin improved to about 40 percent required (where 50 percent was neutral) up to 305 KCAS. It was then determined that flutter testing could continue to higher airspeeds if the pilot needed to apply a "small" wheel force to augment the trim. The pilot had been instructed to reduce airspeed if there was a problem during the flutter testing, and had done so during an uncommanded roll to the left on the previous flight. Telemetry data from the accident flight revealed that at initiation of the upset, the pilot attempted to level the wings and raise the nose, but the airplane continued to diverge from stable flight, and it continued to accelerate beyond the airplane’s demonstrated flight diving speed. It is undetermined if the pilot could have reduced the speed of the airplane in time, during the initiation of the upset, so that the airplane would not diverge. After the accident, the company conducted high-speed wind tunnel tests, and found that lateral stability decreased with increasing Mach and angle of attack (AOA). Lateral stability became negative (unstable) above Mach 0.83, and rudder input intended to augment lateral trim above a certain Mach could aggravate the situation. In addition, a TEU elevator input would increase AOA, and also result in deteriorated lateral stability. High speed wind tunnel data also revealed that roll authority deteriorated above Mach 0.86, and by Mach 0.88, the aileron upper and lower surfaces were both in separated flow regions. The follow-on flutter test airplane, which successfully completed the certification requirements, was equipped with vortex generators and thicker trailing-edge ailerons. It also did not require the external trim device needed on the accident airplane due to improvements in manufacturing.

Probable cause

The manufacturer's incomplete high-Mach design research, which resulted in the airplane becoming unstable and diverging into a lateral upset.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record IAD03MA049
Event ID
20030515X00671
Case number
IAD03MA049
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: 7ed76902c2b770365a5eed69a050c01551794e6041f6e04e6f3627f715ab7075; retrieved 2026-09-20T19:17:11.383Z.