FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL97LA036 · Robinson R22

31 Jan 1997 · Wiggins, MS, United States

Robinson R22 · Accident: in flight collision with object while maneuvering

From Gulfport Biloxi International Airport (GPT) to Linwood Airport (MS06)

Report a problem

Event

NTSB case
ATL97LA036
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
0
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
General aviation
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

Robinson R22

Aircraft type
Robinson R22
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
N8319T
Operator
Unknown
Onboard fatalities
Unknown
Route
From Gulfport Biloxi International Airport (GPT), Gulfport, MSTo Linwood Airport (MS06), MS
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
Part 91: General Aviation
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
Maneuvering · hover
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
In flight collision with object
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Pole
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 › Clearance, misjudged

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The student pilot was conducting a solo cross-country flight, and had completed two legs of the flight before landing at Wiggins. According to the operator, the student was hovering to a parking ramp to refuel, when the main rotor blades struck a utility pole. The operator said that the student pilot saw the utility pole, but misjudged the rotor blade clearance. No mechanical problems with the helicopter were reported by the student.

Probable cause

the student pilot misjudged rotor blade clearance from a utility pole, which resulted in a collision. The proximity of the pole was a related factor.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL97LA036
Event ID
20001208X07260
Case number
ATL97LA036
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. 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: e94b9f2d5809e1ad96448fbb559c3f5e6c428da1bfcac6ff887ec126e902c7e5; retrieved 2026-09-22T20:24:41.312Z.