Fairchild SA227-AC N831BC
3 December 2013 · La Alianza, United States · Fatal
Summary
On 3 December 2013 at about 00:10 local time, a Fairchild SA227-AC registered N831BC, operated by IBC Airways Inc, was involved in an accident near La Alianza, United States. 2 people were on board and 2 died. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 00:10
- Classification
- Accident
- Location
- La Alianza, United States
- Coordinates
- 18.3844, -66.5883
- Aircraft
- Fairchild SA227-AC
- Registration
- N831BC
- Category
- Airplane
- Year built
- 1986
- Engines
- 2
- Operator
- IBC Airways Inc
- Operating rule
- Part 135: Air Taxi & Commuter
- Phase of flight
- Not recorded
- Route
- Santo Domingo → San Juan
- Aircraft damage
- Destroyed
- Weather
- VMC
- Light
- Night
- NTSB number
- ERA14MA060
People
2 people died.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 2 | 2 | 0 | 0 | 0 |
Probable cause
The flight crew's excessive elevator input during a rapid descent under night lighting conditions, which resulted in the overstress and breakup of the airplane. Contributing to the accident was an initial loss of airplane control for reasons that could not be determined because postaccident examination revealed no mechanical anomalies that would have precluded normal operation.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
The captain and first officer were conducting an international cargo flight in the twin-engine turboprop airplane. After about 40 minutes of flight during night visual meteorological conditions, an air traffic controller cleared the airplane for a descent to 7,000 ft and then another controller further cleared the airplane for a descent to 3,000 ft and told the flight crew to expect an ILS (instrument landing system) approach. During the descent, about 7,300 ft and about 290 kts, the airplane entered a shallow left turn, followed by a 45-degree right turn and a rapid, uncontrolled descent, during which the airplane broke up about 1,500 ft over uneven terrain. The moderately loaded cargo airplane was not equipped with a flight data recorder or cockpit voice recorder (CVR) (although it previously had a CVR in its passenger configuration) nor was it required by Federal Aviation Administration (FAA) regulations. There were also no avionics on board with downloadable or nonvolatile memory. As a result, there was limited information available to determine what led to the uncontrolled descent or what occurred as the flight crew attempted to regain control of the airplane. Also, although the first officer was identified in FAA-recorded radio transmissions several minutes before the loss of control and it was company policy that the pilot not flying make those transmissions, it could not be determined who was at the controls when either the loss of control occurred or when the airplane broke up. There was no evidence of any in-flight mechanical failures that would have resulted in the loss of control, and the airplane was loaded within limits. Evidence of all flight control surfaces was confirmed, and, to the extent possible, flight control continuity was also confirmed. Evidence also indicated that both engines were operating at the time of the accident, and, although one of the four propeller blades from the right propeller was not located after separating from the fractured hub, there was no evidence of any preexisting propeller anomalies. The electrically controlled pitch trim actuator did not exhibit any evidence of runaway pitch, and measurements of the actuator rods indicated that the airplane was trimmed slightly nose low, consistent for the phase of flight. Due to the separation of the wings and tail, the in-flight positions of the manually operated aileron and rudder trim wheels could not be determined. Other similarly documented accidents and incidents generally involved unequal fuel burns, which resulted in wing drops or airplane rolls. In one case, the flight crew intentionally induced an excessive slide slip to balance fuel between the wings, which resulted in an uncontrolled roll. However, in the current investigation, the fuel cross feed valve was found in the closed position, indicating that a fuel imbalance was likely not a concern of the flight crew. In at least two other events, unequal fuel loads also involved autopilots that reached their maximum hold limits, snapped off, and rolled the airplane. Although the airplane in this accident did not have an autopilot, historical examples indicate that a sudden yawing or rolling motion, regardless of the source, could result in a roll, nose tuck, and loss of control. The roll may have been recoverable, and in one documented case, a pilot was able to recover the airplane, but after it lost almost 11,000 ft of altitude. During this accident flight, it was likely that, during the descent, the flight crew did regain control of the airplane to the extent that the flight control surfaces were effective. With darkness and the rapid descent at a relatively low altitude, one or both crewmembers likely pulled hard on the yoke to arrest the downward trajectory, and, in doing so, placed the wings broadside against the force of the relative wind, which resulted in both wings failing upward. As the wings failed, the propellers simultaneously chopped through the fuselage behind the cockpit. At the same time, the horizontal stabilizers were also positioned broadside against the relative wind, and they also failed upward. Evidence also revealed that, at some point, the flight crew lowered the landing gear. Although it could not be determined when they lowered the gear, it could have been in an attempt to slow or regain control of the airplane during the descent. Although reasons for the loss of control could not be definitively determined, the lack of any preexisting mechanical anomalies indicates a likelihood of flight crew involvement. Then, during the recovery attempt, the flight crew's actions, while operating under the difficult circumstances of darkness and rapidly decreasing altitude, resulted in the overstress of the airplane.
Quoted verbatim from the NTSB record.
Other Fairchild SA227 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 20 Aug 2013 | Fairchild SA227 | Sucre, Bolivia | Linea Area Commuter "Aerocon" LTDA | No injuries | - |
| 10 Nov 2012 | Fairchild SA227-AC | Minneapolis, Minnesota, United States | Bemidji Aviation Services Inc | No injuries | - |
| 17 Apr 2015 | Fairchild SA227 AC | Rifle, Colorado, United States | Key Lime Air Corporation | No injuries | - |
| 11 Mar 2011 | Fairchild SA227-AC | Seattle, Washington, United States | Ameriflight Inc | No injuries | - |
| 2 Jan 2010 | Fairchild SA227 | Somerset, Kentucky, United States | Locair, Inc | No injuries | - |
| 22 Mar 2016 | Fairchild SA227 | Tierra del Fuego, Argentina | - | Unknown | - |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 10 Feb 2013 | Bell 206B | Acton, California, United States | Orbic Air | Fatal | 3 |
| 23 Jul 2013 | Schweizer 269C | Gary, South Dakota, United States | - | Minor injuries | - |
| 6 Sep 2013 | Cessna 150G | Denver, Colorado, United States | - | No injuries | - |
| 20 Oct 2013 | Wohaska John PARSONS STILES GYRO | Festus, Missouri, United States | Wohaska John S | Minor injuries | - |
| 10 Feb 2013 | Bell 206B | Shandon, California, United States | Sycan Corp DBA | No injuries | - |
| 17 Apr 2013 | Poole Robert C Jr VAN'S | Salisbury, North Carolina, United States | - | Minor injuries | - |