British HS 125-700A N232TN
1 November 2006 · Fort Lauderdale, Florida, United States · No injuries
Summary
On 1 November 2006 at about 07:33 local time, a British HS 125-700A registered N232TN was involved in an accident near Fort Lauderdale, Florida, United States. 12 people were on board and nobody was injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 07:33
- Classification
- Accident
- Location
- Fort Lauderdale, Florida, United States
- Nearest airport
- Fort Lauderdale/Hollywood Intl (KFLL)
- Coordinates
- Not recorded
- Aircraft
- British HS 125-700A
- Registration
- N232TN
- Category
- Airplane
- Engines
- 2
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Executive/Corporate
- Phase of flight
- Not recorded
- Route
- Toluca → Fort Lauderdale
- Aircraft damage
- Substantial
- Weather
- VMC
- Light
- Night
- NTSB number
- MIA07FA005
People
Nobody was injured.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 12 | 0 | 0 | 0 | 12 |
Probable cause
The failure of the flight crew to extend the landing gear. Contributing to the accident was the inoperative audible landing gear warning system.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
As the flight approached Fort Lauderdale/Hollywood International Airport, Fort Lauderdale, Florida, the flight crew prepared for a visual approach to the runway and advised the air traffic controller that the field was in sight. According to the pilot, he was distracted by trying to locate the runway for a visual approach. A review of the "Before Landing" and "Close In" checklists for the airplane revealed that both checklists contained landing gear verification tasks; however, although the copilot stated that he read from the checklist, the cockpit voice recorder (CVR), which captured other cockpit conversations, recorded no checklist challenge-response callouts. During the landing, the airplane touched down on the runway with its landing gear retracted and slid about 2,600 feet before coming to a stop, sustaining substantial damage to a structural component and fire damage to the bottom of the fuselage. Following touchdown, the CVR recorded that the pilot asked what happened to the landing gear and that the copilot responded, "We never put it down." Although the airplane was equipped with an audible landing gear warning system designed to alert the flight crew that the landing gear is not extended when the airplane is otherwise configured for landing, the CVR captured no sounds that could be associated with the landing gear warning horn, and the pilot reported that he did not hear a warning. Postaccident testing of the airplane’s landing gear system revealed that it operated normally using the normal and emergency extension systems and that the cockpit landing gear visual annunciators and standby indicators correctly indicated the landing gear position. However, the audible landing gear warning system did not operate. Examination of the electrical wiring for the warning system revealed that a wire labeled "68CA8" was fractured and separated from the "CA" relay; this separation rendered the landing gear warning horn inoperative. Metallurgical examination of the 68CA8 wire revealed that the fracture features were consistent with overstress; however, the source of the overstress condition was not identified. According to the airplane’s maintenance records, the CA relay and its immediate area were inspected 7 months and 22 days before the accident, and the airplane had operated for 60 hours (accumulating 43 cycles) since the inspection. According to the airplane manufacturer, there is no preflight test that a flight crew could perform to determine the operational status of the audible landing gear warning system. However, because the audible landing gear warning system and the cabin altitude warning system shared the CA relay, the fractured 68CA8 wire would also have rendered the cabin altitude warning system inoperative, and the operational status of the cabin altitude warning system is a preflight check item for flight crews. Therefore, the anomaly that rendered the gear warning system inoperative would be detectable during a flight crew’s preflight check because the cabin altitude warning would fail to function. However, a review of available maintenance and discrepancy records revealed no indication that any flight crews had previously detected and reported an inoperative cabin altitude warning system, and the accident crewmembers provided no information about their preflight observations of the status of the cabin altitude warning system. Therefore, it could not be determined when the 68CA8 wire fracture occurred. The pilot was employed by the airplane’s owner. The investigation found that the pilot’s U.S. commercial airman certificate (issued on the basis of his Mexican pilot license) was not valid for the carriage of persons for compensation or hire. Further, Federal Aviation Administration (FAA) records indicated that the pilot did not hold a U.S. airman medical certificate and that his U.S. airman certificate did not include a type rating for the accident airplane or an instrument rating (the accident flight was operated under instrument flight rules). Additionally, the pilot had not completed a pilot proficiency check within the preceding 12 calendar months. Further, the copilot held only a U.S. private pilot certificate (issued on the basis of his Mexican pilot license) that did not include an instrument rating. Although there is insufficient evidence to indicate that any of these flight crew discrepancies were directly related to the cause of the accident, the FAA determined that these discrepancies represented noncompliance with numerous Federal Aviation Regulations (FARs). According to the FARs, the pilot was not authorized to act as pilot-in-command of the accident flight, and the copilot was not authorized to act as a required crewmember of the accident flight.
Quoted verbatim from the NTSB record.
Other British HS-125 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 19 Oct 1999 | British HS 125-700A | Fayetteville, North Carolina, United States | - | No injuries | - |
| 20 Apr 2014 | British HS 125 700A | Saltillo, Mexico | - | Fatal | 8 |
| 10 Nov 2015 | British HS 125 700A | Akron, Ohio, United States | Execuflight | Fatal | 9 |
| 12 Jul 2026 | British HS-125-700 | Santa Lucia, Mexico | - | No injuries | - |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 25 Apr 2006 | Lake LA-4-200 | Lake Wales, Florida, United States | - | Minor injuries | - |
| 1 Mar 2006 | Mooney M20J | Fort Pierce, Florida, United States | - | Minor injuries | - |
| 26 Apr 2006 | Beechcraft A24R | Okeechobee, Florida, United States | - | Fatal | 2 |
| 15 Jul 2006 | Dahlstrom - Piel Emeraude CP-30 | Venice, Florida, United States | David G. Dahlstrom | No injuries | - |
| 19 Jul 2006 | Piper PA-34-200 | Deland, Florida, United States | Phoenix East Aviation, Inc. | Serious injuries | - |
| 28 Apr 2006 | Howard DGA-15P | Merritt Island, Florida, United States | - | No injuries | - |