NTSB CAROL · Event
Event MIA96LA026
Aircraft involved
Probable cause & findings
THE PILOTS FAILURE TO FOLLOW THE VISUAL APPROACH SLOPE INDICATOR AND MAINTAIN A PROPER GLIDEPATH DURING APPROACH. CONTRIBUTING TO THE ACCIDENT WAS PILOT FATIGUE.
Factual narrative
On November 23, 1995, about 0048 eastern standard time, a Piper PA-32-300, N44CQ, registered to Otto Enterprises, Inc., collided with two fences and the approach lights during approach to runway 9 left at Fort Lauderdale-Hollywood International Airport, Fort Lauderdale, Florida, while on a 14 CFR Part 91 personal flight. Visual meteorological conditions prevailed at the time and an instrument flight rules flight plan was filed. The aircraft received substantial damage and the commercial-rated pilot and two passengers received minor injuries. The flight last departed Savannah, Georgia, on November 22, 1995, about 2200. The pilot stated that the visibility was greater than 10 miles. He was cleared by air traffic controllers to fly the instrument landing system approach to runway 9 left. He flew the approach to the decision height and continued the approach under visual flight rules. He was "possibly" distracted by the street lights on the interstate highway and the approach lights appeared to be the same color as the street lights. The runway lights were set to a low intensity. The aircraft struck the approach lights and the landing gear was sheared off. The aircraft struck another object and then touched down on top of another set of approach lights. The aircraft touched down on the ground and skid to a stop. Examination of the accident site was performed by an FAA inspector. The aircraft first contacted the approach lights mounted on poles in the middle of Interstate 95. Components of the aircrafts landing gear were found on the interstate. The aircraft then collided with a jet blast fence and came to rest short of the approach end of the runway. The pilot told the FAA inspector that the visual approach slope indicator was working. The pilot also told the FAA inspector that he had worked for 2 hours that day and departed Delaware about 1630. He flew for 4 hours to Savannah and then another 3 hours to Fort Lauderdale. He stated his passengers were asleep at the time of the accident and that he was feeling some fatigue. See inspector statement. WHILE MAKING THE NIGHT APPROACH WITH VISIBILITY GREATER THAN 10 MILES, THE PILOT FLEW THE ILS APPROACH TO THE DECISION HEIGHT, AND THEN CONTINUED THE APPROACH VISUALLY. THE AIRCRAFT COLLIDED WITH THE APPROACH LIGHTS AND SEVERED THE LANDING GEAR. THE AIRCRAFT STRUCK A BLAST FENCE AND ADDITIONAL APPROACH LIGHTS BEFORE COMING TO REST SHORT OF THE RUNWAY. THE PILOT STATED HE WAS POSSIBLY DISTRACTED BY LIGHTS ON THE INTERSTATE HIGHWAY JUST BEFORE THE RUNWAY. HE ALSO SAID THE VISUAL APPROACH SLOPE INDICATOR WAS OPERATING, AND THAT HE WAS FATIGUED FROM A LONG DAY AND 7 HOURS OF FLYING. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1995_MIA96LA026.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 (pilot fatigue). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- SKYbrary (Eurocontrol) 2023 · SKYbrary article
Pilot Fatigue — SKYbrary Knowledge Base
SKYbrary pilot fatigue review — circadian biology, biomathematical models (SAFE/FAID), commuting impacts, regulatory frameworks (FAR 117 + EU 83/2014).
- NASA NTRS 2023 · Presentation
Nasa Pilot Fatigue Research: Past, Present & Future
Pilot fatigue research at NASA Ames has a long history, initiated by a Congressional request to investigate the magnitude of fatigue, sleep loss and circadian disruption in flight operations, and how …
- FAA CAMI 2022 · CAMI technical report
Pilot Fatigue and Sleep Patterns in Long-Range and Ultra-Long-Range Operations
Field study of crew sleep and alertness during ultra-long-range commercial operations. Combines actigraphy, sleep diaries, and PVT-B reaction tests.
- NASA NTRS 2019 · Technical Memorandum (TM)
San Francisco Bar Pilot Fatigue Study
The purpose of this study was to evaluate the extent of fatigue among San Francisco Bar Pilots (Maritime Pilots) and its potential impact on safety, and to make recommendations concerning how the risk…
- NASA NTRS 2019 · Conference Proceedings
Pilot Fatigue and Circadian Desynchronosis
Pilot fatigue and circadian desynchronosis, its significance to air transport safety, and research approaches, were examined.
- Embry-Riddle Scholarly Commons 2024 · Conference paper
Benefits associated with improving fatigue regulations for cargo pilots
This study investigated the potential business benefits of improving fatigue regulations for cargo pilots in Brazil. The research objectives were to compare fatigue levels between cargo and passenger …
Browse the full corpus — academia portal ↗