# NTSB IAD03MA049: Sino-Swearingen SJ30-2, N138BF, Loma Alta, TX, April 26, 2003

- Type: NTSB accident investigation
- Classification: Accident · Fatal · Major investigation · Final report
- Date: April 26, 2003, 10:05 local (15:05 UTC)
- Place: Loma Alta, TX
- Coordinates: 29.872777, -100.96083
- Nearby events: https://openairdocs.org/map.md?lat=29.8728&lon=-100.9608&mi=10
- Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping)
- Highest injury: Fatal
- Injuries: 1 fatal
- Status: Completed, report March 30, 2005
- Report: Approved by Office Director
- Parties: Williams International, FAA/AAI-100, Sino Swearingen
- NTSB case key (mKey): 56888
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=IAD03MA049
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/56888/pdf
- Page: https://openairdocs.org/ntsb/IAD03MA049

## Probable cause

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

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Loss of control - in flight, descent
  - aircraft control - not possible
  - inadeq substantiation process,inadeq documentation, manufacturer (cause)
  - information insufficient, manufacturer
- In flight collision with terrain/water, descent - uncontrolled
  - terrain condition - ground

## Analysis

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.

## Factual narrative

HISTORY OF FLIGHT

On April 26, 2003, at 1005 central daylight time, a Sino-Swearingen Aircraft Corporation (SSAC) SJ30-2, N138BF, serial number 002, was destroyed when it impacted terrain near Loma Alta, Texas.  The certificated airline transport pilot was fatally injured.  Visual meteorological conditions prevailed for the flight, which departed on an instrument flight rules flight plan from San Antonio International Airport (SAT), San Antonio, Texas, at 0911.  The local test flight was conducted under 14 CFR Part 91.

At the time of the accident, the airplane was undergoing flutter testing for Federal Aviation Administration (FAA) type certification.  SSAC Report 30-2222, "Flight Flutter Certification Test Plan for SSAC SJ30-2," delineated the flutter testing requirements, which included the Federal Air Regulation (FAR) Part 23.629 requirement that the airplane be demonstrated to be free from flutter, control reversal, and divergence up to the "demonstrated flight diving speed" (Vdf/Mdf).  The testing was to be conducted in two phases, with the first phase planned to clear the airplane to its "maximum operating limit speed" (Vmo/Mmo) of 320 KCAS/Mach 0.83, and the second phase, to clear it to its Vdf/Mdf of 372 KCAS/Mach 0.90.

Phase 1 flutter testing had been successfully completed.  The first flutter mission of phase 2, flight test number 230, was flown one day before the accident flight, with the same pilot onboard.  The objective of that flight was to complete flutter test points 1-12 (Mach  0.844) and 1-13 (Mach 0.864).  Test point 1-12 was completed, and subsequently, the airplane went into a uncommanded roll to the left, which the pilot recovered from.  Afterwards, during test point 1-13, a discrepancy was noted between the pilot's displayed airspeeds and those reported by a chase plane pilot, so the pilot terminated the flight.

After the flight, the pilot realized that he had incorrectly set up the airspeed display in the test airplane, and was flying faster than his airspeed indicated.  In addition, the pilot reported, that during the flight, he had felt a "rumble" in conjunction with the left roll.  In his notes, he had written, ".855", and immediately below that, "Abrupt LH Roll [space] Rumble", and beneath that, "Rudder Input?"

According to the project's flutter consultant, a Designated Engineering Representative (DER), a possible explanation for the rumble was Mach buffet.  However, to help confirm there wasn't an in-flight mechanical problem with the airplane, flight test personnel assigned a second SSAC pilot as a backseat chase plane observer for the next (accident) flight, flight test number 231.

The chase plane was a contracted Northrop T-38 jet, N638TC, with a pilot and the second SSAC test pilot onboard.  The accident flight was also being monitored in a telemetry van in Rock Springs, Texas, by the flutter consultant and three SSAC personnel.

Prior to the test flight, a mission briefing, led by the accident test pilot, was conducted via conference call between the San Antonio-based personnel and the telemetry van personnel.  According to a briefing participant, all of the flight test cards were covered, "including the test limitations, test set-up, test points, weight and balance, airspace operational considerations, aircraft limitations, maintenance actions since last flight, instrumentation status, and chase aircraft procedures."  A number of witnesses also noted that the test points briefed were 1-14 (Mach 0.884), and 1-15 (Mach 0.894) if conditions permitted.

An "SSAC Flight Briefing Guide" was also utilized, which included a review of hazard analyses, and abnormal/emergency procedures.  During the briefing, the test pilot stated that he was responsible for safety of flight.

The flutter consultant also stated that he had, during previous discussions, advised that for the purpose of flutter testing, if the pilot ran out of aileron/elevator trim, the tests could still be completed, even if the pilot had to hold aileron/elevator force to steady the airplane.  He further stated, however, that the continuance of the testing would never override the pilot's decision as to whether the control forces were unacceptable or hazardous.

According to the flutter consultant, after takeoff, the accident airplane climbed to 39,000 feet, and prepared for a shallow dive along an easterly track for flight test point 1-14.  A telemetry lock was then obtained.  However, when the airplane reached indicated Mach 0.875, the test pilot called "Mark" on the radio.  [An optional test point "14A" (Mach 0.874) was listed on the flutter test card; however, on the previous day's flight, it had been crossed out.]    After the "Mark" was received, the pilot initiated a single pulse input to the elevator.  After checking the telemetry strips, the consultant then gave a "Go" for a single pulse to the aileron, followed by another "Go" for a single pulse to the rudder.  Telemetry van personnel noted that all the modes excited were "well damped."

Telemetry van personnel also reported that after the pulses were completed, the test pilot stated that the uncommanded roll to the left (which was experienced on the previous flight), did not occur.  There was also no mention of a rumble.  In addition, the chase plane pilots confirmed that there were no mechanical anomalies evident on the accident airplane.

The flutter consultant further stated that the accident airplane subsequently turned back to the west and began to climb back to 39,000 feet to prepare for the [easterly] dive to the 1-14 point.  Discussion between the pilot and telemetry van personnel included the fact that the 1-14 point might be the last one of the mission due to fuel concerns, particularly for the chase plane.

Following telemetry lock, the airplane began a shallow dive.  At indicated Mach 0.884, the pilot called "Mark."  Each control surface was again pulsed by the pilot, and the responses were again "well damped."

Following the final pulse, the pilot was cleared to the next test point, 1-15 (indicated Mach 0.894), "if flight conditions permitted the test pilot to do so."  However, the pilot did not acknowledge the clearance, but instead, reported that the airplane was rolling to the right, and he couldn't stop it.

In a written statement, the chase plane pilot confirmed that after the 1-14 test point had been completed, the test pilot was cleared to accelerate to the 1-15 test point, if able.  At that time, the accident airplane appeared to be in a shallow right bank with the chase plane less than 500 feet above and 500 feet behind it.  According to the chase plane pilot, "very soon thereafter," about 30,000 feet, the accident airplane began rolling to the right.  The rolling maneuver appeared to be stable, and continued unchanged until ground impact.  The accident airplane appeared to remain intact throughout the event, and no parts were seen departing the airframe.  After the accident airplane began to roll, and the test pilot stated that he couldn't stop it, the chase pilot called, "get out" twice.  The accident pilot responded that he couldn't get out, that there were too many "g's."

The second SSAC test pilot, who had been in the back of the chase plane, also reported that the accident sequence began after the completion of the 1-14 test point.  During the sequence, the chase plane was not close enough to observe the accident airplane's control positions; however, the second SSAC test pilot observed the accident airplane's nose to be "a little low," and in an approximately 30-degree right bank after test point 1-14 was completed.  A few seconds later, the accident airplane entered a "barrel-roll type maneuver" to the right, then continued to roll, and increased its dive angle until ground impact.

When the second SSAC test pilot saw the first roll, his first thought was, "what did he do that for?"  Then he saw

## Aircraft

- Registration: [N138BF](https://openairdocs.org/deregistered/N138BF-2003-06-17), registration cancelled 2003-06-17, S/N 002, built 2000 (OpenAirDocs)
- Reported make and model: Sino-Swearingen SJ30-2
- Registry model: [Sino Swearingen Acft SJ30-2](https://openairdocs.org/model/sino-swearingen-acft-sj30-2) (registry code 8780113) (OpenAirDocs)
- Registry engine: [Williams FJ-44 series](https://openairdocs.org/engine/williams-fj-44-series) (registry code 66000, turbo-fan) (OpenAirDocs)
- Category: Airplane
- Serial number: 002
- Airframe hours: 284
- Engines: Williams International FJ-44-2A 2300 lbs thrust turbo fan; Williams International FJ44-2A 2300 lbs thrust turbo fan
- Damage: Destroyed
- Flight: Flight test, Part 91
- Registered owner: Sino-Swearingen Aircraft Company
- Airworthiness certificate: Special, Experimental (Special)
- Last inspection: Continuous airworthiness, January 28, 2003, 60 hours before
- Departed: SAT, San Antonio, TX
- Flight plan: IFR

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 59; injuries: fatal; airline transport; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, valid medical--w/ waivers/lim; seat: left; flight hours: 12,000 total, 625 in this make and model, 39 in the last 90 days, 17 in the last 30 days, 3 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Wind: 330° at 10 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 61 °F, dew point 41 °F
- Altimeter: 30.15 inHg
- Observed at: DRT, 35 nm away

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20030426036959A](https://openairdocs.org/incident/20030426036959A), Apr 26, 2003: Sino SJ302, Del Rio, TX, Destroyed, 1 fatal. (-23) N138BF, a SJ30-2 experimental/research and development aircraft was conducting flight test operations involving high speed flutter testing. The aircraft…

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
