FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX97LA061 · McDonnell Douglas MD-600N

21 Nov 1996 · Flagstaff, AZ, United States

McDonnell Douglas MD-600N · Accident: abrupt maneuver

From Flagstaff Pulliam Airport (FLG) to an unrecorded destination

Report a problem

Event

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

McDonnell Douglas MD-600N

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
N630N
Operator
Unknown
Onboard fatalities
Unknown
Route
From Flagstaff Pulliam Airport (FLG)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
Other
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
Abrupt maneuver
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

  • Ground personnel › Air/ground communications, disregarded
  • Pilot in command › Air/ground communications, inaccurate
  • Pilot in command › Altitude, inattentive

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

NTSB narrative

The helicopter was being flight tested to validate certification criteria for height velocity curves at a maximum gross weight and zero airspeed at a high density altitude airport. On the fourth test profile, the pilot allowed the aircraft to descend below the target altitude of 800 feet agl by almost 70 feet. The ground test engineers observed the drift down and didn't advise the pilot because they assumed he had already begun the autorotation after he had made the 3 second call, and also they believed their ground equipment was inaccurate. The pilot delayed the autorotation for about 8 to 12 seconds and then lowered the collective. The aircraft landed hard exceeding the maximum load for the landing gear system. The horizontal speed at touchdown was 52 knots instead of the target speed of 65 knots. The test helicopter was equipped with standard analog altimeters with pointers that have a lag time instead of the more accurate real time digital altimeters.

Probable cause

The pilot's inattention to the altitude and inadvertent late entry into an autorotation maneuver below the established minimum test altitude with a helicopter operating at maximum gross weight in a high density altitude environment that led to a subsequent hard landing. Contributing were the lack of positive communications between ground test personnel and the pilot regarding the low altitude, and the lack of accurate in-flight and ground altimeter equipment.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX97LA061
Event ID
20001208X07083
Case number
LAX97LA061
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: 4dd9f28680413e81eab409d17145b5939fdb34704905aedcc6c1c448d1a5b68c; retrieved 2026-09-22T20:45:03.871Z.