MIA07FA005 · British Aerospace HS 125-700A
British Aerospace HS 125-700A · Accident: wheels up landing
From Adolfo López Mateos International Airport (MMTO) to Fort Lauderdale Hollywood International Airport (KFLL)
Event
- NTSB case
- MIA07FA005
- 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
- 0 · 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
British Aerospace HS 125-700A
- Aircraft type
- British Aerospace HS-125
- 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
- N232TN
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Adolfo López Mateos International Airport (MMTO), TolucaTo Fort Lauderdale Hollywood International Airport (KFLL), Fort Lauderdale, 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
- Landing · flare/touchdown
- 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
- Wheels up landing
- 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
- Flightcrew › Checklist, not followed
- Flightcrew › Gear extension, not performed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA07FA005
- Event ID
- 20061114X01639
- Case number
- MIA07FA005
- 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: a8703a2c03c041e14d7dd9175533457fa0eaf90a1560264a7ba58cc7e880463c; retrieved 2026-09-22T04:16:23.665Z.