FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA02TA082 · Aerospatiale SA319B Alouette III

9 Apr 2002 · Altoona, FL, United States

U.S. Forest Service Aerospatiale SA319B Alouette III · Accident during landing

From Altoona, FL to an unrecorded destination

Report a problem

Event

NTSB case
MIA02TA082
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
Government
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

Aerospatiale SA319B Alouette III

Aircraft type
Aerospatiale SA319
Category
Helicopter
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
N2UH
Onboard fatalities
Unknown
Route
From Altoona, FLTo not recorded
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
Public Aircraft
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
Miscellaneous/other
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

  • Pilot in command › Cyclic, improper use of
  • Pilot in command › Operation with known deficiencies in equipment, initiated

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The accident pilot noted that the day before the accident date, the normal brakes were inoperative. Maintenance was notified of the brake discrepancy, and he was advised by maintenance personnel that the brakes would be inspected that evening during the planned 25-hour inspection. The next morning (day of the accident), he became aware the brakes had not been repaired and he believed he was informed while in dispatch of a search and rescue mission; the site was located approximately 40 miles from the helibase. He expressed concern to the chief pilot about operation of the helicopter with inoperative brakes, but the chief pilot felt it was alright for the flight to proceed. Since the assigned mission was for search and rescue, the chief pilot suggested and he concurred, "that due to possible lives at stake, I could accept the mission." The flight departed, proceeded to the search area with negative results, then elected to return to the helibase. After arrival at the helibase, he performed a hover power check. After completion of the hover power check, he maneuvered the helicopter over the landing pad. The chief pilot was standing by with chocks to chock the wheels upon landing as was previously arranged due to the inoperative brakes. He made a normal touchdown and as the nose gear lowered, he expected the chief pilot to chock the wheels. As the helicopter settled, it rolled forward towards the hangar, and he attempted to control the forward movement by positioning of the flight controls, aware of the cyclic limitations during ground operations. He could not arrest the forward movement and was concerned about contacting the hangar; the chocks were not in place. The next thing he recalled was feeling the helicopter vibrating, followed by the cyclic making extreme movements in the cockpit. The pilot also stated that the helicopter encountered what he felt were normal vibrations, and was not positive the helicopter encountered complete ground resonance. He attempted to lift to a hover to correct the situation but was not sure if the helicopter even became airborne. The passenger stated that after landing, he noticed out of the corner of his eye the helicopter appeared to be rolling forward. He later recalled the pilot stating that the helicopter was lifting. He noticed a vibration, and noted that the nose lifted to what he thought was a normal angle. The vibration turned into violent shaking which was throwing him around in his seat. The helicopter moved to over grass and started moving down a little faster. He noticed that parts from the helicopter started separating either when the helicopter quit moving towards the ground or the nose landing gear was fully compressed. An object hit his left arm and thigh coming to rest on the floor near his feet. He noted the pilot trying to secure the engine, smelled jet fuel, and evacuated the wreckage. The chief reported that the pilot made a normal approach which ended with a power check at a low hover. The pilot then maneuvered the helicopter over the helipad to land and after touching down, the helicopter began to roll forward slightly. He stated that the pilot attempted to pick up to a hover and when only the main landing gears were on the ground but fully extended, the helicopter began to shake. He reported hearing a loud sound or crash and the pilot and passenger exited the helicopter. He secured the engine with the emergency fuel shutoff lever. He further stated that with respect to the brakes, he and the director of maintenance (DOM) were both aware that the brakes were inoperative the day before, and on the day of the accident before the accident flight, he was made aware the brakes were not repaired. He called the DOM who advised the brakes would be fixed on the accident date, and he (chief pilot) considered the inoperative brakes to be a minor deficiency; the helicopter was not taken out of service. He further reported that due to the search and rescue mission, the urgency and considerations changed, and that he believed the inoperative brake situation needed to be addressed promptly but was not an airworthy issue when compared for example with a fixed wing airplane. Review of the "Aircraft Contract Daily Diary" sheet for the day before the accident revealed, "...Hydraulic brakes not working-mechanic notified." According to a FAA airworthiness inspector, maintenance personnel from the owner of the helicopter performed maintenance on the wheel brakes of the helicopter the day before the accident but did not have a proper fitting to bleed the brakes. Maintenance personnel were scheduled to bleed the brakes on the day of the accident but did not. No maintenance record entry was made in the permanent maintenance records indicating the brakes were inoperative. The helicopter did not have an FAA approved minimum equipment list (MEL).

Probable cause

The intentional operation of the helicopter with known deficiencies in equipment (inoperative normal brakes), and the pilot's improper use of the cyclic flight controls after the helicopter started rolling following touchdown.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA02TA082
Event ID
20020416X00516
Case number
MIA02TA082
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: d3d95e9a5bbea9ac0368c86103c1c60f4e2de73c65e9e9d40588c8fd62d7769f; retrieved 2026-09-18T21:19:22.803Z.