# Incident 20040722017229I: Amtr EXCALIBUR, Sanford, ME, July 22, 2004

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: July 22, 2004, 19:00 local time
- Place: Sanford, ME
- Airport: Sanford Municipal
- Damage: Minor damage
- Phase of flight: Forced Landing
- Operating rules: General operating rules (Part 91)
- Location: 43.4392° N, 70.7742° W: Placed by OpenAirDocs: center of Sanford, ME, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=43.4392&lon=-70.7742&mi=10
- Aircraft: N24208, registered now (https://openairdocs.org/aircraft/N24208) (OpenAirDocs)
- Registry model: Lavertu Darcy M EXCALIBUR (registry code 05615VM, https://openairdocs.org/model/lavertu-darcy-m-excalibur) (OpenAirDocs)
- Registry engine: Rotax SEE BOMBADIER (registry code 55555, https://openairdocs.org/engine/rotax-see-bombadier) (OpenAirDocs)
- Reported make and model: AMTR EXCALIBUR
- Reported engine: ROTAX ROTAX*
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 4,500 total, 3 in this make and model, 60 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20040722017229I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) ON 3RD FLIGHT OF NEW AIRCRAFT AT SFM, PILOT OBSERVED THAT IT DID NOT CLIMB AS WELL AS ON PREVIOUS FLIGHT. TACH AND OTHER ENGINE INDICATIONS APPEARED NORMAL. WHILE ON A WIDE DOWNWIND FOR RUNWAY 14, THE ENGINE SUDDENLY STOPPED. HIS ALTITUDE WAS APPROXIMATELY 500 FEET OVER A HEAVILY WOODED AREA, AND HE COULD NOT GLIDE TO THE AIRPORT. HE THEN MADE AN EMERGENCY LANDING IN A THICKET OF SMALL TREES AND BUSHES. THE LANDING WAS VERY GENTLE AND THE SMALL TREES SUPPORTED THE AIRCRAFT ABOUT 7 FEET ABOVE THE GROUND. THE PILOT WAS ALONE AND WAS NOT INJURED. THE AIRCRAFT SUSTAINED ONLY MINOR DAMAGE WITH ONLY A FEW TEARS TO THE FABRIC. PROPERTY DAMAGE WAS NEGLIGIBLE.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.