NYC06LA039 · Rogers Lancair 360
Rogers Lancair 360 · Accident: loss of engine power during takeoff
From Martha's Vineyard Airport (MVY) to Martha's Vineyard Airport (MVY)
Event
- NTSB case
- NYC06LA039
- 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
- 1 · 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
Rogers Lancair 360
- Aircraft type
- Rogers LANCAIR 360
- 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
- N360JR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Martha's Vineyard Airport (MVY), Vineyard Haven, MATo Martha's Vineyard Airport (MVY)
- 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
- Takeoff
- 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 engine power
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot/mechanic had modified the newly installed engine, and the airplane received its airworthiness certificate on the day prior to the accident. On the day of the accident, the pilot/mechanic performed one flight in the morning, after which, he was observed making repairs to the airplane. The pilot stated to a mechanic at the airport that the engine was "running hot," and he thought the ignition timing was "off." After the pilot/mechanic completed repairs on the airplane, he departed for a second flight. During climbout, as the airplane approached the mid-point of the runway, the pilot stated, "juliet romeo return to base." The controller cleared the pilot to land, and the airplane impacted trees to the right of runway 15, resulting in a post-crash fire. Examination of the engine revealed no mechanical anomalies, however, the engine accessory section was consumed by fire, and several accessories could not be tested.
Probable cause
A loss of engine power for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC06LA039
- Event ID
- 20051216X01981
- Case number
- NYC06LA039
- 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: 8b65f3027e67f5de425cf8918784a74a0a22601466ff6edac419a94ab9aad806; retrieved 2026-09-20T17:44:20.911Z.