NYC01LA027 · O Loughlin WAG-A-BOND
O Loughlin WAG-A-BOND · Accident: total loss of engine power (non-mechanical) en route
From 3B1 to an unrecorded destination
Event
- NTSB case
- NYC01LA027
- 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
O Loughlin WAG-A-BOND
- Aircraft type
- O Loughlin WAG-A-BOND
- 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
- N51AT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 3B1To 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
- En route · climb to cruise
- 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
- Total loss of engine power (non-mechanical)
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Estimated position: the centre of Greenville, ME, the place the record names. Not the accident site.
NTSB narrative
The airplane departed, and while approximately 2 miles west of the airport, the pilot initiated a climbing turn from 2,500 feet msl to 3,000 feet. Passing 2,800 feet, the airplane lost engine power. The pilot checked the position of the fuel valves, selected the carburetor heat to 'ON' and mixture to full rich. He noted that after the loss of power, the propeller continued to windmill. The pilot attempted a forced landing to a golf course. While on final for a fairway, and flying towards rising terrain, the pilot had to trade airspeed for altitude to clear some trees. After clearing the trees, airspeed was inadequate to cushion the landing, and the airplane touched down hard, collapsing the landing gear. The airplane came to a stop, and the pilot exited under his own power. Examination of the engine and engine accessories revealed no preimpact failures or malfunctions.
Probable cause
Total loss of engine power for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC01LA027
- Event ID
- 20001215X45426
- Case number
- NYC01LA027
- 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: 80947f71740d7e6711de5f2e14c82ef8d06acfcf653783497acf2c3ff04aea98; retrieved 2026-09-22T12:21:35.482Z.