- Date
- June 25, 2013, 13:00 local (18:00 UTC)
- Place
- Ely, MN
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N715SBAviat A-1B
- Defining event
- Landing: Loss of control on ground
- Weather
- Visual (VMC) · Day
- Status
- Completed · report December 2, 2013
- Report
- Approved by Office Director
- NTSB office
- Central Region
- Parties
- Federal Aviation Administration - Minneapolis FSDO, Wipaire Inc.
- FAA report
- 20130625011479A
- Case key
- 87311
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
The pilot’s failure to maintain control of the amphibious airplane during the water landing.
Findings · 3
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Analysis
The pilot reported that the accident occurred when he was making water landings in the amphibious airplane. He stated that he noted no anomalies during his first landing. He said the lake surface had “light ripples,” and the wind speed was less than 5 knots. The pilot stated that his second landing approach and touchdown were also initially uneventful; however, shortly after the airplane touched down, it began to roll and yaw toward the left, and the left wing contacted the water. The airplane came to rest partially submerged, nose-low, in the lake. An examination of the recovered wreckage revealed substantial damage to several float struts and spreader bars; however, all examined component damage was consistent with overstress, with no preexisting material defects observed. Because the damage to the amphibious float components occurred during the accident, they likely did not contribute to the initial loss of control. Therefore, given the pilot's report of light wind, the pilot should have been able to maintain airplane control throughout the water landing.
Factual narrative
On June 25, 2013, at 1300 central daylight time, an Aviat Aircraft model A-1B amphibious airplane, N715SB, was substantially damaged during a water landing on Shagawa Lake, near Ely, Minnesota. The airline transport pilot and his passenger were not injured. The airplane was registered to and operated by a private individual, under the provisions of 14 Code of Federal Regulations Part 91, without a flight plan. Day visual meteorological conditions prevailed for the pleasure flight that departed Ely Municipal Airport (KELO), near Ely, Minnesota, about 1245. The pilot reported that after a short local area flight he began to make water takeoff-and-landings on Shagawa Lake toward the southeast. The pilot reported that his first landing was uneventful and that there were no anomalies with the airplane. He described the lake surface condition as having “light ripples” with a wind speed of less than 5 knots. He stated that his second landing approach and touchdown were again uneventful; however, shortly after the touchdown the airplane began to roll and yaw toward the left until the left wing made contact with the water. The airplane ultimately came to rest partially submerged nose-low in the lake. The fuselage, wings, and amphibious floats were damaged during the accident sequence. An examination of the recovered wreckage was completed by Federal Aviation Administration (FAA) inspectors and an aerospace engineer employed by the amphibious float manufacturer. Their examination revealed substantial damage to several float struts and spreader bars. The left rear float strut attachment fitting with fractured portions of lower airframe longeron tube and the inboard sections of the left and right rear spreader bar mounting tubes were submitted to the National Transportation Safety Board (NTSB) Materials Laboratory for additional examination. The examined components exhibited fracture features that were consistent with overstress. Additionally, no preexisting material defects were noted during the NTSB laboratory examination. The nearest aviation weather reporting station was located at Ely Municipal Airport (KELO), Ely, Minnesota, about 6.25 miles south of the accident site. At 1252, the KELO automated surface observing system reported: wind from 200 degrees at 4 knots, visibility 10 miles, sky clear, temperature 28 degrees Celsius, dew point 12 degrees Celsius, and an altimeter setting of 29.82 inches of mercury.
Aircraft
- Registration
- N715SB
- Reported as
- Aviat A-1B
- Category
- Airplane
- Serial number
- 2051
- Airframe hours
- 688
- Engine
- Lycoming O-360-A1P, 180 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Annual · May 16, 2013
- Departed
- KELO · Ely, MN
- Destination
- KELO · Ely, MN
- Airport
- Shagawa Lake
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 62
- Injuries
- None
- Certificates
- Flight engineer, Airline transport
- Airplane ratings
- Multi-engine land, Single-engine sea, Single-engine land
- Instrument ratings
- Airplane
- Medical
- Class 1, Without waivers/limitations
- Last flight review
- May 5, 2013
- Seat
- Front
- Flight hours
- 17,000 total · 40 in this make and model · 15,000 as pilot in command · 200 in the last 90 days · 69 in the last 30 days · 1 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 200° at 4 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 82 °F, dew point 54 °F
- Altimeter
- 29.81 inHg
- Observed at
- KELO, 6 nm away
Docket · 4
The files NTSB released with the investigation on September 5, 2013, on NTSB’s docket system: statements, records, photos and specialists’ reports. 1.4 MB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.