NTSB CAROL · Event
Event LAX96FA122
Registry · N27989
FAA Aircraft Registry record.
Make / Model
PIPER PA-31-350
Year of manufacture
1979 · 17 years old at event
Engine
LYCOMING TI0-540 SER (310 hp)
Seats / Engines
8 seats · 2 engines
Last airworthiness date
19790227
ADS-B equipped
Yes — Mode-S A2CB7D
Registrant of record
CSC DELAWARE TRUST CO TRUSTEE
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
the failure of the pilot to maintain directional control of the aircraft after landing. Contributing to the accident was the icy runway conditions with poor braking.
Factual narrative
HISTORY OF FLIGHT
On February 28, 1996, at 0950 hours mountain standard time, a Piper PA-31-350, N27989, was substantially damaged during landing at Grand Canyon Airport, Arizona. The aircraft was being operated as sightseeing Flight 89 by Las Vegas Airlines, Las Vegas, Nevada. The flight was conducted as a 14 CFR Part 135 operation. Instrument meteorological conditions prevailed for the flight and an IFR flight plan had been filed. The pilot and nine passengers were uninjured. The flight originated at North Las Vegas on the morning of the accident at 0730 hours Pacific standard time. The pilot stated in his report that the Grand Canyon weather was above instrument approach weather minimums at the time of departure. He stated that "approaching the canyon I received ATIS information Juliet; 1,200 scattered, visibility 3/4 mile." The Grand Canyon ILS/DME runway 3 approach requires a minimum of a 200-foot ceiling and 1/2 mile visibility. According to the Federal Aviation Administration (FAA) at 0900, information "Juliet" reported: measured ceiling 1,300 feet broken; 3,000 feet overcast; visibility 3/4 mile with light fog; temperature 23 degrees Fahrenheit; dew point 21 degrees Fahrenheit; wind calm; and the altimeter was 30.03 inHg. When the pilot contacted the Grand Canyon Air Traffic Control Tower (ATCT), he stated he had "Juliet". No additional weather information was provided the pilot. The pilot stated that after landing he drifted to the left. He said he tried to correct, but the plane skidded off the runway. According to the pilot, he had operated the deice boots one time prior to landing to eliminate accumulated ice. The pilot contacted the Grand Canyon ATCT at 0939, while on the ILS approach. At 0941, the local controller advised the pilot that a vehicle reported the braking action as poor, the pilot acknowledged. At 0946, the pilot reported "HAPLY" DME fix inbound and the pilot was cleared to land. At 0947, the weather was recorded as indefinite 400 feet obscured and 1/4 mile snow and fog. A written statement was obtained from the airport manager. About 30 minutes after the accident he took photographs of the airframe icing that was still present on all leading edges and propellers of the aircraft. He stated that the ice was 1/4 to 1/2 inch thick and extending 1 to 2 inches above and below the leading edge of the surfaces. Some ice had broken away during the accident sequence. The manager also stated that there was about 1 inch of snow on the runway at the time of the accident. They had plowed the runway to a width of 130 feet earlier in the morning. According to an airport attendant in a vehicle near the runway, the airplane landed hard to the left of the runway centerline.
PERSONNEL INFORMATION
According to the pilot/operator accident report form, the ATP rated pilot had a total of 4,480 total flight hours with 1,670 hours in the make and model of the accident airplane. According to the FAA records, the pilot's last airman competency/proficiency check for FAR 135.293, 297, and 299 was accomplished on November 28, 1995. The pilot was given a postaccident flight check on March 1, 1996.
AIRCRAFT INFORMATION
The airplane was maintained under an FAA Approved Airplane Inspection Program (AAIP). The last inspection, event no. 3, had been conducted on February 21, 1996, at a total time of 15,261.1 hours. According to the pilot, all of the airplane's systems were working with no deferred maintenance items. According to FAA operations specifications dated February 10, 1989, the use of the autopilot in-lieu of required second-in-command was permitted for instrument flight in the accident airplane.
METEOROLOGICAL INFORMATION
The Grand Canyon ASOS, (automated surface observation system), reported the weather at the time of the accident as: indefinite 400 feet overcast; 1/4 mile in fog and snow; temperature 24 degrees Fahrenheit; dew point 22 degrees Fahrenheit; wind 160 degrees at 3 knots per hour; and the altimeter was 30.04 inHg. The operator stated that in his opinion the ASOS system had not been reliable for the last 3 months. Consequently, when weather was in question, he would call the ATCT one or more times for an observation from tower personnel which he did on the day of the accident. According to the operator, the pilot obtained preflight weather information from DUAT, ASOS, and had made a call to the Grand Canyon tower. The weather was above landing minimums and forecast to stay above. The operator stated that for the last 3 months the ASOS had not been reliable. According to the pilot's report, he received ATIS information 'Juliet' approaching Grand Canyon and it was 1,200 scattered with visibility of 3/4 miles. According to the FAA, information 'Juliet' was reporting, 50 minutes before the accident: a measured ceiling 1,300 feet broken; 3,000 feet overcast; visibility 3/4 mile in fog; temperature 23 degrees Fahrenheit; dew point 21 degrees Fahrenheit; wind calm; and the altimeter was 30.03 inHg. At the time of the accident, the ASOS was reporting indefinite 400 feet overcast with 1/4 mile in fog and snow. The ILS approach requires a minimum of a 200-foot ceiling and 1/2 mile visibility. The braking action was reported as poor due to snow and ice. The airplane landed to the left of the runway centerline and collapsed the landing gear as it slid sideways. A light ice buildup was observed on the leading edges of the airframe by airport personnel. According to the pilot, he had operated the deice boots just prior to landing. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1996_LAX96FA122.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 (icing, maintenance, autopilot). 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 2023 · Faculty research project
Reconfigurable Guidance and Control Systems for Emerging On-Orbit Servicing, Assembly, and Manufacturing (OSAM) Space Vehicles
Dynamic response to emergent situations is a necessity in the on-orbit servicing, assembly, and manufacturing (OSAM) field, because traditional on-orbit guidance and control (G&C) cannot respond effic…
- Embry-Riddle Scholarly Commons 2019 · Journal article (IJAAA)
Satellite Maintenance: An Opportunity to Minimize the Kessler Effect
Recently, there has been an emphasis on the growing problem of orbital debris. While the advantages of placing satellites into space are numerous, advances in satellite technology combined with the gr…
- Embry-Riddle Scholarly Commons 2015 · Conference paper
The Implementation of Safety Management Systems in Maintenance Operations
Literature for Safety Management Systems (SMS) that apply to flight operations is abundant, but there is a limited supply of SMS-related literature for maintenance operations.
- 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…
- NASA NTRS 2026 · Contractor Report (CR)
Icing Physics Studies Using the 3D SIDRM Test Article: 2023 Icing Tests Analysis
In-flight icing is an important safety issue and is a factor that affects aircraft design and performance. Newer regulations are driving a need for improvements in airframe and engine icing simulation…
- arXiv 2025 · arXiv preprint
Multi-Agent Deep Reinforcement Learning for UAV-Assisted 5G Network Slicing: A Comparative Study of MAPPO, MADDPG, and MADQN
The growing demand for robust, scalable wireless networks in the 5G-and-beyond era has led to the deployment of Unmanned Aerial Vehicles (UAVs) as mobile base stations to enhance coverage in dense urb…
Browse the full corpus — academia portal ↗