Nord (Sncan) Stampe SV4C accident near Taneytown, Maryland, June 21, 2008
On June 21, 2008 at about 3:00 pm local time, a Nord (Sncan) Stampe SV4C, registered N97264, was substantially damaged in an accident during landing near Taneytown, Maryland (Greer airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's misjudgment of the airplane's altitude during the final approach.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 21, 2008 · about 3:00 pm local time
- Place
- Taneytown, Maryland · Greer · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Nord (Sncan) Stampe SV4C
- Registration
- N97264 · no longer on the register · serial 1100
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
According to the pilot of the Nord Stampe SV4C, he made three successful landings at the 1,500-foot-long, 100-foot-wide grass airstrip. During the fourth landing attempt's final approach, the airplane's main landing gear became entangled in the last 20 to 25 feet of a 2-foot-high wheat field. The airplane then nosed over, and came to rest inverted on the runway. Neither the pilot nor the Federal Aviation Administration inspector on scene reported any preimpact mechanical anomalies with the airplane. The pilot also noted that he should not have tried to land so close to the approach end of the runway.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Landing area undershoot during landing defining event
- Roll over during landing
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
- cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
Pilot
- Certificate: commercial pilot
- Ratings: single-engine land; instrument: airplane
- Flight time: 7,521 hours in all; 362 in this make and model; 6 in the last 90 days; 5 in the last 30 days
- Last flight review: October 1, 2007
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: rear
- Injury: no injuries
The aircraft
- Airframe total time: 1,582.2 hours
- Last inspection: condition inspection, June 1, 2007
- Maximum gross weight: 1,815 lb
- Seats: 2
- Landing gear: fixed
- Engine: Renault 4PEi (piston); 0 hours total
The flight
- Departed from: MD20 Taneytown MD at 2:50 pm
- Destination: MD20 Taneytown MD
- Flight plan: none
- Runway 29, 1,500 ft by 100 ft
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 79°F (26°C), dew point 63°F (17°C)
- Altimeter: 30.09 inHg
- Observation at 2:52 pm from DMW, 5 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
