# Incident 20030527009449I: Amtr ULTRAPELICAN, Middleburg, VT, May 27, 2003

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: May 27, 2003, 14:53 local time
- Place: Middleburg, VT
- Damage: Minor damage
- Phase of flight: To Init Climb(1st Pwr Reduct)
- Operating rules: General operating rules (Part 91)
- Aircraft: N412JP, a cancelled registration (https://openairdocs.org/deregistered/N412JP-2014-08-28) (OpenAirDocs)
- Registry model: Pratt John A ULTRAVIA PELICAN-PL (registry code 056046Z, https://openairdocs.org/model/pratt-john-a-ultravia-pelican-pl) (OpenAirDocs)
- Registry engine: Amateur-built UNKNOWN ENG (registry code 99999, https://openairdocs.org/engine/amateur-built-unknown-eng) (OpenAirDocs)
- Reported make and model: AMTR ULTRAPELICAN
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 6,000 total, 132 in this make and model, 50 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20030527009449I

## Narrative

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

(-23) PILOT DEPARTED FROM 6B0 WITH ONE PAX IN HIS HOMEBUILT. MADE ONE LANDING ON LAKE DUNMORE, TAXIED BACK AND TOOK OFF. AFTER CLIMB OUT ENGINE TEMP INCREASED BEYOND LIMITS. PILOT RETURNED TOWARDS AIRPORT, WATER TEMP THEN REACHED MAX, AND LOST OIL PRESSURE. PILOT LANDED AIRCRAFT ONE HALF MILE SHORT OF AIRPORT (6B0) IN A FARMER'S FIELD. NO INJURIES. DAMAGE TO BOTH NOSE GEAR ON FLOATS. POPPED OUT WINDSHIELD AND CRACKED FIBERGLASS FUSELAGE AT FLOAT ATTACHMENT. AIRCRAFT MOVED TO OWNERS/PILOTS RESIDENCE.

## Other reports on N412JP (1)

Matched to the same aircraft by N-number and date.

- [Accident 20050712014749A](https://openairdocs.org/incident/20050712014749A), Jul 12, 2005: Amtr ULTRAPELICAN (N412JP), Middlebury, VT, Destroyed. (-23) After departure from Middlebury, VT airport, the pilot of the homebuilt aircraft stated that he experienced a power loss and the aircraft started to lose…

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.