NTSB CAROL · Event
Event FTW00LA078
Registry · N245DH
FAA Aircraft Registry record.
Make / Model
FAIRCHILD SA227-AT
Year of manufacture
1985 · 15 years old at event
Engine
AMA/EXPR UNKNOWN ENG
Seats / Engines
12 seats · 2 engines
Last airworthiness date
19851008
ADS-B equipped
Yes — Mode-S A242E5
Registrant of record
UAS TRANSERVICES INC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The flight crew's failure to extend the landing gear. Contributing factors were the flight crew's non-compliance with the checklist, the pilot-in-command's diverted attention as a result of the loss of instrument approach/runway lighting, the partial failure of the instrument approach/runway lighting system, and the partial failure of the intercom system.
Factual narrative
On January 28, 2000, at 2130 central standard time, a Swearingen SA-227-AT twin-engine airplane, N245DH, was substantially damaged during a wheels up landing at the Fayetteville Airport, Fayetteville, Arkansas. The airline transport pilot, acting as the captain, and the commercial pilot, acting as the first officer, were not injured. The airplane was registered to Banc of America Leasing & Capital LLC of San Francisco, California, and operated by Ameriflight, Inc., of Burbank, California. Night visual meteorological conditions prevailed and an instrument flight rules flight plan was filed for the 14 Code of Federal Regulations Part 135 air taxi cargo flight. The flight originated from Tulsa, Oklahoma, and was terminating at the time of the accident. According to the 4,116-hour captain, the crew experienced a problem with the crew intercom system during departure, and the first officer (flying pilot) had to "repeat his requests three or four times" before the captain could hear him. The crew decided they would notify the maintenance personnel when they arrived at their destination. The captain reported that air traffic control issued a clearance to descend to 3,000 feet "at pilot's discretion." The crew initiated their descent at a "later than normal distance" from the airport. The first officer needed to reduce the power below 25 percent torque in order to expedite the descent, which set off the gear warning horn. The sound "eventually became part of the background noise." The captain added that at 2 miles from the final approach fix (FAF), he asked the tower to dim the runway lights. At that time, the runway and approach lights went out and the crew lost sight of the runway. While the captain was asking the tower to turn the lights back on, the first officer called "gear down, syncs off, speeds high, below the line check list." The captain did not hear the first officer's callout and did not lower the landing gear. The captain stated that he did not hear the first officer's callout "either because of the conversation [he] was having with the tower or because of the intercom difficulties." As the approach continued, the first officer had a problem slowing the airplane to proper approach speed. The airplane touched down on the runway with the landing gear retracted, "slid" approximately 2,500 feet and exited the left side of the runway. According to the FAA inspector, who examined the airplane, two pressure bulkheads were structurally damaged. On departure for the night air taxi cargo flight, the flight crew experienced a problem with the crew intercom system. The crew initiated their descent at a 'later than normal distance' from the airport, and as a result, a power reduction below 25 percent torque was required, which set off the gear warning horn. The sound 'eventually became part of the background noise.' During the approach, the captain asked the tower to dim the runway lights. At that time, the runway and approach lights went out and the crew lost sight of the runway. While the captain was asking the tower to turn the lights back on, the first officer called 'gear down, syncs off, speeds high, below the line check list.' The captain did not hear the first officer's callout and did not lower the landing gear. The captain stated that he did not hear the first officer's callout 'either because of the conversation [he] was having with the tower or because of the intercom system difficulties.' As the approach continued, the first officer had a problem slowing the airplane to proper approach speed. The airplane touched down on the runway with the landing gear retracted, 'slid' about 2,500 feet and exited the left side of the runway. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2000_FTW00LA078.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Just Culture in Aviation: A Metaphorical Study on Aircraft Maintenance Students
Just Culture, a sub-dimension of safety culture, has been a prominent and debated topic in aviation safety in recent years.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Performance PRISM: A Comprehensive Framework For Performance Measurement In Aircraft Maintenance
Aircraft maintenance is governed by rigorous safety requirements and high operational complexity, demanding robust performance measurement frameworks to ensure optimal maintenance practices.
Browse the full corpus — academia portal ↗