FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA10LA277 · Rutter Herbert G LONG EZ

21 May 2010 · Wakefield, VA, United States

Rutter Herbert G LONG EZ · Accident: loss of control in flight on approach

From Altoona Blair County Airport (AOO) to Suffolk Executive Airport (SFQ)

Report a problem

Event

NTSB case
ERA10LA277
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
1 · 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
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

Rutter Herbert G LONG EZ

Category
Airplane
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
N91HR
Operator
Unknown
Onboard fatalities
Unknown
Route
From Altoona Blair County Airport (AOO), Altoona, PATo Suffolk Executive Airport (SFQ), Suffolk, VA
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
Approach · VFR pattern final
Defining eventThe 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
Loss of control in flight
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

  • Personnel issues › Task performance

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

NTSB narrative

Acquaintances of the pilot indicated that his intended destination was an airport located about 200 miles to the south of his departure airport. A witness reported that he observed the airplane approach, and after completing the first legs of a traffic pattern, it over flew the turn onto the final approach path. The airplane then executed a left 360 degree turn about 700 feet above ground level. After the turn, the airplane was again past the extended runway centerline. The airplane continued the left turn for several seconds, and then followed with a sharp turn to the right. The airplane impacted terrain about 250 feet prior to the runway threshold; ground scars indicated that it struck in a right wing down attitude.

At the time of the accident, the wind velocity was about 4 knots and the sky was clear of clouds. The majority of the witness observations were corroborated by global positioning system (GPS) data that was recovered from a unit in the airplane. Examination of the GPS data, the airplane, and the engine did not reveal any evidence of preimpact mechanical failures. No definitive reasons for the pilot's decision to land at the accident airport, or his difficulties in aligning with the runway, were discovered. The pilot's most recent Federal Aviation Administration third-class medical certificate expired about 22 months prior to the accident. Shortly thereafter, the FAA withdrew the pilot's eligibility for medical certification, and his eligibility for medical certification was never re-established. Neurological evaluations, family member observations, and autopsy findings were consistent with the pilot experiencing progressive cognitive decline due to Alzheimer’s disease.

Probable cause

The pilot’s failure to properly align the airplane with the final approach path to the runway and his subsequent loss of control during his attempts to correct the flight path. Contributing to the accident was the pilot’s progressive cognitive decline due to Alzheimer’s disease.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA10LA277
Event ID
20100521X04342
Case number
ERA10LA277
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 586d2fe823c6b2b6abaadc1cfcaf3b730ddc5674a6fc454989a0d5b3a29bd9cc; retrieved 2026-09-13T20:48:56.699Z.