FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX00LA219 · Piper PA-28-161

9 Jun 2000 · Mesa, AZ, United States

Und Aerospace Flight Tranning Piper PA-28-161 · Accident: in flight encounter with weather during landing

From Ivanovo South Airport (IWA) to an unrecorded destination

Report a problem

Event

NTSB case
LAX00LA219
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

Piper PA-28-161

Aircraft type
Piper PA-28
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
N115ND
Onboard fatalities
Unknown
Route
From Ivanovo South Airport (IWA)To 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
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
Landing
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 encounter with weather
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 › Directional control, not obtained/maintained
  • Pilot in command › Remedial action, not performed

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

NTSB narrative

The student pilot was practicing stop-and-go landings. On the first landing the airplane veered to the right side of the runway, and struck a distance remaining sign. After the collision, the airplane taxied to the ramp without further incident. The 1050 ATIS reported winds were from 180 degrees at 12 knots, gusting to 20 knots. Witnesses at the accident site reported that the winds were variable in direction with gusty conditions. The demonstrated crosswind component for the airplane is 17 knots. According to the chart, the effective crosswind at the time of the accident was 17 knots. The student had received dual instruction in the performance of crosswind landings.

Probable cause

the failure of the pilot to maintain directional control in that he failed to properly position the ailerons during his landing roll. Gusty, crosswind conditions, from a direction and velocity that equaled the aircraft's maximum demonstrated crosswind capability, were a factor in this accident.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX00LA219
Event ID
20001212X21261
Case number
LAX00LA219
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: afaa314a328a6eae56cd00279c36887b08eec594abf7c81263e32b39c0f6d3cb; retrieved 2026-09-22T12:49:23.695Z.