SEA07CA130 · Aircraft Mfg & Dev. Co. (AMD) CH 2000
Aircraft Mfg & Dev. Co. (AMD) CH 2000 · Accident: loss of control in flight during initial climb
From Castle Airport (MER) to Castle Airport (MER)
Event
- NTSB case
- SEA07CA130
- 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
- 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
Aircraft Mfg & Dev. Co. (AMD) CH 2000
- Aircraft type
- Aircraft MFG Dev Co (amd) CH-2000
- 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
- N363AM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Castle Airport (MER), Atwater, CATo Castle Airport (MER)
- 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
- Initial climb
- 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
- Loss of control in flight
- 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
- Stall/mush
- 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
- Dual student › Stall/mush, inadvertent
- Pilot in command(cfi) › Remedial action, delayed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight instructor said the instructional flight was to prepare the student for his stage two check, which was to be followed by his first solo flight. The student had received 41.2 hours of instruction, with 5.4 hours in this make/model aircraft. The flight instructor had planned for a simulated engine failure after takeoff; it was the flight instructor's first practice simulated engine failure after takeoff in this make/model aircraft. He pulled the throttle to idle, but the student held the yoke in the climb attitude as opposed to nosing the airplane down for best glide speed. The flight instructor said that he realized the airspeed was low and the aircraft was in a high rate of descent, but his remedial attempts did not prevent a hard landing. The airplane's firewall was wrinkled, and the empennage and horizontal stabilizer were bent.
Probable cause
The student pilot's inadvertent stall/mush during a simulated power loss after takeoff and the flight instructor's delayed remedial action, which resulted in a hard landing. A contributing factor was the flight instructor's lack of familiarity with the make/model of aircraft.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA07CA130
- Event ID
- 20070617X00751
- Case number
- SEA07CA130
- 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: 9f854f94408142fce8c4d84da7b7ff022bd8147e04cd3324cc25466aae35829c; retrieved 2026-09-22T03:49:13.474Z.