NTSB CAROL · Event
Event MIA96LA152
Registry · N821RR
FAA Aircraft Registry record.
Make / Model
BRITTEN-NORMAN BN-2A-9
Year of manufacture
1973 · 23 years old at event
Engine
LYCOMING TI0-540 SER (310 hp)
Seats / Engines
10 seats · 2 engines
Last airworthiness date
19970203
ADS-B equipped
Yes — Mode-S AB3619
Registrant of record
AIR CHARTER INC DBA
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
Failure of the student pilot to maintain the proper descent rate resulting in a hard landing. Contributing to the accident was: the failure of other maintenance personnel to remove tape that was placed by company personnel over each static port before washing the airplane, inadequate preflight of the airplane by the student pilot, his failure to activate the alternate static source, and his lack of total experience in make and model airplane.
Factual narrative
On June 8, 1996, about 0645 Atlantic standard time, a Piper PA-32R-301, N821RR, registered to a private individual, was substantially damaged on landing at the Fernando Luis Ribas Dominicci Airport, San Juan Puerto Rico. Visual meteorological conditions prevailed at the time and no flight plan was filed for the 14 CFR Part 91 instructional flight. The student pilot, the sole occupant, was not injured. The flight originated about 15 minutes earlier. The student pilot failed to observe and remove tape that was covering each static port during the preflight inspection of the airplane. He stated he used the manufacturer's inspection checklist, but it indicates that the static ports are required to be inspected to verify that they are clear. The purpose of the flight was to perform touch-and-go landings and after departure during the downwind leg, the airspeed indicator indicated 0. He lowered the landing gear selector handle but the landing gear did not extend and the landing gear indicator lights circuit breaker popped. He reset the circuit breaker several times and continued in the pattern flying over the runway about 50 feet above ground level. The flight remained in the traffic pattern and the circuit breaker again popped several times. While on final approach during the second pattern, all three landing gear down and locked lights were illuminated and he landed the airplane just beyond the threshold. During the landing roll the landing gear collapsed and the airplane came to rest upright. The pilot did not activate the alternate static source and he stated that the nose baggage door opened at touchdown. Witnesses on the airport reported seeing the airplane flying in the traffic pattern at near full power. One witness stated he did not detect a change in engine sound between the initial climb and the descent for landing. According to an FAA airworthiness inspector who examined the runway and airplane the day of the accident, he reported that he observed 10 propeller ground scars on the runway. He also reported that the nose landing gear down lock mechanism was sheared and both main landing gears exhibited evidence of being forced rearward and upward. Also noted was that both main landing gear strut assemblies were bent aft. Ground scars on the runway indicate that after the landing gear collapsed , the airplane slid on the ground then became airborne momentarily before coming to rest upright on the runway. Additionally, the three propeller blades were observed to be curled forward and both upper engine mounts were failed. Both trunnion fitting assemblies for each main landing gear were failed. Visual examination of the fracture surfaces of the engine mounts and the trunnion fitting assemblies revealed no evidence of preimpact failure or malfunction. The FAA inspector also stated that the damage to the airplane was consistent with a hard landing and he observed tape over each static port. The airplane was equipped with an alternate static source. According to the Director of Maintenance for Caribbean Helicorp., he placed electrical tape over both static ports 2 days before the accident in preparation for washing the airplane. Another company employee washed the airplane but both failed to remove the tape over each port. The pilot had accumulated a total of 3.6 hours solo in the accident airplane and had performed no more than 15 landings during solo flight. Flight testing of a different airplane equipped with a similar pitot/static system and both static ports taped was accomplished. The flight test revealed that the airspeed indicator would indicate during the takeoff roll and also during the initial climb. While climbing through 500 feet, the airspeed indicator began to decrease and at 500 feet indicated 0. The airspeed indicator again began to indicate at 300 feet. Supplemental information prepared by a metallurgist provided by the pilot indicated that "...the wings were permanently damaged due to the bending force exerted by the impact during the touch down." Two days before the accident, tape had been placed over each static port in preparation for washing the airplane. The person who placed the tape and the person who washed the airplane did not remove the tape after the airplane had been washed. During the preflight inspection of the airplane, the student pilot did not observe or remove the tape covering each static port. The airplane preflight inspection checklist indicates that each static port is required to be inspected to verify each is clear. The flight departed to perform touch-and-go landings and during the downwind leg, the airspeed indicator indicated 0. The pilot stated he lowered the landing gear via the normal method but the gear indicator lights circuit breaker popped several times while in the pattern. Witnesses reported hearing the airplane flying in the traffic pattern at near full power. The pilot flew over the runway and remained in the pattern. While on final approach during the second pattern, all gear indicator lights indicated that the gear was down and locked. The airplane landed hard causing all three gears to collapse and the nose baggage door to open. Flight tests confirm that the airspeed indicator would indicate during the takeoff roll until the flight was about 400 feet above ground level at which time the airspeed indicator would indicate 0. The pilot had a total of 3.6 hours total solo time in the accident airplane and no more than 15 solo landings. He did not activate the equipped alternate static source. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1996_MIA96LA152.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 ↗