The worst has happened - battery died mid-air, Solo plummeted into the ocean

[Travelfox]

....And I'm deeply gutted.

This has never happened to me before, to have a battery die while in flight. It was fully charged and at that time was still over 50%. Like most of you I've had my share of accidental and human error crashes, missing drone, and even missing and non-working parts after a crash-and-fall. But I've always managed to FIND the drone, repair or replace the parts.

To have it just stop and dive into the ocean - I feel helpless. It's not so much the drone (as we - multiple drones and parts owners know) but the GoPro and the memory card and the clips I haven't uploaded.

I'd like to post the last video from my feed, in honor of this great bird:

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

After the pause I turned around, getting ready to return, but the preview on my phone froze with no battery or signal levels.


My friends who were in the black truck watching the drone said it just stopped mid-air and dove into the water. I've stayed there for a long time after they left and went home, looking for it in case it floats or gets washed away nearby. It was a sad, sad day for me.

 

[DJMc]

Bad luck and comiserations.

I'm an engineer by profession and inclination, but sure I'm not the only one who finds that last screenshot 'Waiting to hear from Solo' quite poignant.

You do get attached to these things when the do their thing well for you for so long.

 

[Pedals2Paddles]

What makes you think the battery died? Without logs, you have no indication what caused it to crash. The screen shot you posted has no battery data because the solo is no longer connected.

 

[RichWest]

To have it just stop and dive into the ocean - I feel helpless. It's not so much the drone (as we - multiple drones and parts owners know) but the GoPro and the memory card and the clips I haven't uploaded.

Sorry for your loss...

I've used 16gb cards since forever, it forces me to swap cards or offload every 3-4 flights...lessons learned.

What makes you think the battery died?

My friends who were in the black truck watching the drone said it just stopped mid-air and dove into the water.

 

[Pedals2Paddles]

Yes, I read that. That doesn't mean the battery died. A witness some distance away seeing it fall isn't narrowing it down much. I'm asking if he has some logs or other evidence like seeing the voltage tank or something. Anything that specifically indicates it being the battery. Or if it's just a guess.

 

[Pedals2Paddles]

That said, it is the most likely culprit given the video and telemetry seem to have stopped abruptly as pictured. I'd rather a log or description of what the telemetry was showing just before though.

 

[jimloss]

@Travelfox: post the relevant tlog (or last few) from your controller (or Solex if you were saving them there). If it was a sudden loss of power there may be no evidence of this in these logs, but if something else happened to cause this there may be some clues.

 

[RichWest]

That said, it is the most likely culprit given the video and telemetry seem to have stopped abruptly as pictured. I'd rather a log or description of what the telemetry was showing just before though.

We both know if the battery senses a short for any reason, the protection turns off the battery... But agree, a log file would confirm the battery died. So now what?

The loss of the accumulated video is the main heart break. GP & Solo can be replaced, the videos not so much...

 

[User Name]

If you can get a relatively close GPS location from the logs, a diver could probably find it. The water looks pretty clear and shallow. You could also try fishing with a big magnet, you have 4 motors with pretty strong magnets to try to hit. That's a long shot though.

Can't quite tell if it looks like salt water or fresh, and while the Solo and Go Pro are likely a loss outside the plastic parts, the memory card could still be fine. They're pretty resilient.

But yea, leaving videos you want to keep on a memory card is just asking to loose them. Doesn't take it happening too many times before you get religious about clearing them off after each outing.

 

[Pedals2Paddles]

If the logs on the controller or Solex abruptly end prior to the indication of a problem, that is actually a pretty good indication it was a power loss. However it also makes it frustrating because you have no way to know what caused the power loss. It could be a malfunction in the battery. It could be that the battery as not snapped in and vibrated loose. It could be an unlikely but not out of the question hardware problem. As Rich said, a short in the main power that exceeds 140 amps will cause the battery to shut down too, but that's also pretty unlikely.

If the logs show some voltage or current anomaly prior to terminating, it would at least give us a clue in the right direction. I have a feeling this won't be the case though based on that screenshot.

I have seen one person experience a malfunction of the smart battery where it thought it was idle and timed out. In flight, the battery's reported current draw and voltage went to zero, but it was still on and providing power. Then a minute later, the battery turned itself off. As we all know, the battery turns itself off it doesn't sense something hooked up. That sensing malfunctioned and the battery decided it was no longer hooked up to anything, timed out, and shut off in flight. Fortunately the copter was only about 2ft above ground coming in to land at the time. If his logs show this, that would be #2.

 

[skyhax]

Very sorry to hear about that. Wish you had one of these onboard:
https://tinyurl.com/y9nf43oy

Worked here:

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

 

[Travelfox]

What makes you think the battery died? Without logs, you have no indication what caused it to crash. The screen shot you posted has no battery data because the solo is no longer connected.

As far as I know, when the signal is lost between Solo and the remote, it still shows me the battery and even a red bar on the signal meter. Then RTH kicks in and I take over. Like I said I've never had this happen to me before, so I could be wrong about deducing it was battery failure.

I know how to get the log with the controller and the solo through Terminal on my Mac. Given that the bird is already in the ocean:
1. Can I use another Solo to connect to to gather the log?
2. If yes, then I'd assume the log exists in the controller?

 

[Travelfox]

Very sorry to hear about that. Wish you had one of these onboard:
https://tinyurl.com/y9nf43oy

Worked here:

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

Thats a fantastic gadget - thanks for the lead. (Was that your video? That water descent and the sound of the go pro going under water is unnerving)

This is a good reason why I have the Solo set to Return to me VS Return from take off. If there are others who are not aware of this feature, its very handy if you move around while controlling the solo (like a "follow me" smart shot), so it goes back to where the controller is (with you) vs. where you originally took off.

Thanks again, @skyhax I'm definitely getting that for the next one.

 

[jimloss]

As far as I know, when the signal is lost between Solo and the remote, it still shows me the battery and even a red bar on the signal meter. Then RTH kicks in and I take over. Like I said I've never had this happen to me before, so I could be wrong about deducing it was battery failure.

I know how to get the log with the controller and the solo through Terminal on my Mac. Given that the bird is already in the ocean:
1. Can I use another Solo to connect to to gather the log?
2. If yes, then I'd assume the log exists in the controller?

The controller acts as the DHCP server. Your Mac can connect directly to the controller without a Solo on the network.

 

[Travelfox]

But yea, leaving videos you want to keep on a memory card is just asking to loose them. Doesn't take it happening too many times before you get religious about clearing them off after each outing.

And I thought of uploading clips before flying that morning, but it was too nice and I was too eager. This should be a reminder to everyone:
***Transfer your media as often as possible***

 

[Travelfox]

The controller acts as the DHCP server. Your Mac can connect directly to the controller without a Solo on the network.

Thanks @jimloss, @Pedals2Paddles and @RichWest

Here's what I got, sorry its a long one, and would need help deciphering it.

3dr-pairing.conf 100% 33 20.1KB/s 00:00

3dr-solo.log 100% 2023 799.2KB/s 00:00

3dr-solo.log.1 100% 42KB 2.3MB/s 00:00

3dr-solo.log.10 100% 19KB 1.6MB/s 00:00

3dr-solo.log.11 100% 21KB 1.2MB/s 00:00

3dr-solo.log.12 100% 30KB 2.0MB/s 00:00

3dr-solo.log.13 100% 14KB 2.0MB/s 00:00

3dr-solo.log.14 100% 5832 1.1MB/s 00:00

3dr-solo.log.15 100% 16KB 1.9MB/s 00:00

3dr-solo.log.16 100% 9181 1.3MB/s 00:00

3dr-solo.log.17 100% 18KB 2.2MB/s 00:00

3dr-solo.log.18 100% 10KB 1.6MB/s 00:00

3dr-solo.log.19 100% 26KB 2.1MB/s 00:00

3dr-solo.log.2 100% 8834 1.2MB/s 00:00

3dr-solo.log.20 100% 10KB 1.5MB/s 00:00

3dr-solo.log.3 100% 11KB 1.7MB/s 00:00

3dr-solo.log.4 100% 2023 873.8KB/s 00:00

3dr-solo.log.5 100% 10KB 1.5MB/s 00:00

3dr-solo.log.6 100% 11KB 1.4MB/s 00:00

3dr-solo.log.7 100% 24KB 2.6MB/s 00:00

3dr-solo.log.8 100% 18KB 2.0MB/s 00:00

3dr-solo.log.9 100% 24KB 1.9MB/s 00:00

3dr-stm32.log 100% 4749 1.8MB/s 00:00

3dr-stm32.log.1 100% 52KB 3.2MB/s 00:00

3dr-stm32.log.10 100% 19KB 2.2MB/s 00:00

3dr-stm32.log.11 100% 26KB 3.0MB/s 00:00

3dr-stm32.log.12 100% 33KB 3.1MB/s 00:00

3dr-stm32.log.13 100% 14KB 1.7MB/s 00:00

3dr-stm32.log.14 100% 4665 1.1MB/s 00:00

3dr-stm32.log.15 100% 14KB 1.7MB/s 00:00

3dr-stm32.log.16 100% 8234 1.3MB/s 00:00

3dr-stm32.log.17 100% 23KB 3.1MB/s 00:00

3dr-stm32.log.18 100% 11KB 2.0MB/s 00:00

3dr-stm32.log.19 100% 27KB 2.5MB/s 00:00

3dr-stm32.log.2 100% 9047 1.9MB/s 00:00

3dr-stm32.log.20 100% 9698 1.8MB/s 00:00

3dr-stm32.log.3 100% 9530 1.9MB/s 00:00

3dr-stm32.log.4 100% 2796 1.0MB/s 00:00

3dr-stm32.log.5 100% 9534 1.5MB/s 00:00

3dr-stm32.log.6 100% 10KB 1.7MB/s 00:00

3dr-stm32.log.7 100% 26KB 2.8MB/s 00:00

3dr-stm32.log.8 100% 16KB 2.0MB/s 00:00

3dr-stm32.log.9 100% 23KB 2.6MB/s 00:00

3dr-temp.log 100% 220 188.1KB/s 00:00

3dr-temp.log.1 100% 3850 1.4MB/s 00:00

3dr-temp.log.10 100% 1155 643.4KB/s 00:00

3dr-temp.log.11 100% 1760 752.5KB/s 00:00

3dr-temp.log.12 100% 2475 269.7KB/s 00:00

3dr-temp.log.13 100% 605 315.6KB/s 00:00

3dr-temp.log.14 100% 165 95.3KB/s 00:00

3dr-temp.log.15 100% 880 472.2KB/s 00:00

3dr-temp.log.16 100% 385 233.1KB/s 00:00

3dr-temp.log.17 100% 1650 756.1KB/s 00:00

3dr-temp.log.18 100% 660 337.6KB/s 00:00

3dr-temp.log.19 100% 1925 787.9KB/s 00:00

3dr-temp.log.2 100% 550 271.7KB/s 00:00

3dr-temp.log.20 100% 550 277.6KB/s 00:00

3dr-temp.log.3 100% 550 141.5KB/s 00:00

3dr-temp.log.4 100% 55 7.3KB/s 00:00

3dr-temp.log.5 100% 495 255.5KB/s 00:00

3dr-temp.log.6 100% 605 329.2KB/s 00:00

3dr-temp.log.7 100% 1870 804.8KB/s 00:00

3dr-temp.log.8 100% 1045 619.2KB/s 00:00

3dr-temp.log.9 100% 1430 640.0KB/s 00:00

3dr-top.log 100% 4168 1.9MB/s 00:00

3dr-top.log.1 100% 88KB 3.9MB/s 00:00

3dr-top.log.10 100% 29KB 2.7MB/s 00:00

3dr-top.log.11 100% 38KB 3.4MB/s 00:00

3dr-top.log.12 100% 62KB 3.5MB/s 00:00

3dr-top.log.13 100% 12KB 2.6MB/s 00:00

3dr-top.log.14 100% 2740 1.2MB/s 00:00

3dr-top.log.15 100% 19KB 2.6MB/s 00:00

3dr-top.log.16 100% 7526 1.8MB/s 00:00

3dr-top.log.17 100% 30KB 3.2MB/s 00:00

3dr-top.log.18 100% 17KB 2.1MB/s 00:00

3dr-top.log.19 100% 53KB 3.7MB/s 00:00

3dr-top.log.2 100% 13KB 2.2MB/s 00:00

3dr-top.log.20 100% 15KB 2.5MB/s 00:00

3dr-top.log.3 100% 13KB 1.9MB/s 00:00

3dr-top.log.4 100% 801 343.1KB/s 00:00

3dr-top.log.5 100% 12KB 1.8MB/s 00:00

3dr-top.log.6 100% 16KB 2.5MB/s 00:00

3dr-top.log.7 100% 50KB 3.7MB/s 00:00

3dr-top.log.8 100% 27KB 3.1MB/s 00:00

3dr-top.log.9 100% 37KB 3.6MB/s 00:00

3dr-video.log 100% 0 0.0KB/s 00:00

3dr-video.log.1 100% 33KB 2.8MB/s 00:00

3dr-video.log.10 100% 10KB 1.8MB/s 00:00

3dr-video.log.11 100% 14KB 2.1MB/s 00:00

3dr-video.log.12 100% 22KB 2.7MB/s 00:00

3dr-video.log.13 100% 4293 1.0MB/s 00:00

3dr-video.log.14 100% 1085 549.6KB/s 00:00

3dr-video.log.15 100% 7521 2.0MB/s 00:00

3dr-video.log.16 100% 3441 1.0MB/s 00:00

3dr-video.log.17 100% 13KB 1.6MB/s 00:00

3dr-video.log.18 100% 5324 941.7KB/s 00:00

3dr-video.log.19 100% 17KB 2.3MB/s 00:00

3dr-video.log.2 100% 3826 1.2MB/s 00:00

3dr-video.log.20 100% 5172 823.3KB/s 00:00

3dr-video.log.3 100% 4668 1.1MB/s 00:00

3dr-video.log.4 100% 0 0.0KB/s 00:00

3dr-video.log.5 100% 4261 1.2MB/s 00:00

3dr-video.log.6 100% 5430 1.5MB/s 00:00

3dr-video.log.7 100% 16KB 2.6MB/s 00:00

3dr-video.log.8 100% 9332 1.9MB/s 00:00

3dr-video.log.9 100% 13KB 2.2MB/s 00:00

3dr-wifi.log 100% 0 0.0KB/s 00:00

3dr-wifi.log.1 100% 206KB 4.7MB/s 00:00

3dr-wifi.log.10 100% 61KB 3.7MB/s 00:00

3dr-wifi.log.11 100% 86KB 4.4MB/s 00:00

3dr-wifi.log.12 100% 134KB 4.9MB/s 00:00

3dr-wifi.log.13 100% 21KB 2.7MB/s 00:00

3dr-wifi.log.14 100% 5505 1.4MB/s 00:00

3dr-wifi.log.15 100% 46KB 4.2MB/s 00:00

3dr-wifi.log.16 100% 19KB 2.3MB/s 00:00

3dr-wifi.log.17 100% 86KB 4.6MB/s 00:00

3dr-wifi.log.18 100% 31KB 2.8MB/s 00:00

3dr-wifi.log.19 100% 106KB 5.1MB/s 00:00

3dr-wifi.log.2 100% 22KB 2.3MB/s 00:00

3dr-wifi.log.20 100% 30KB 3.1MB/s 00:00

3dr-wifi.log.3 100% 27KB 2.4MB/s 00:00

3dr-wifi.log.4 100% 0 0.0KB/s 00:00

3dr-wifi.log.5 100% 24KB 2.7MB/s 00:00

3dr-wifi.log.6 100% 32KB 3.9MB/s 00:00

3dr-wifi.log.7 100% 100KB 4.9MB/s 00:00

3dr-wifi.log.8 100% 55KB 3.4MB/s 00:00

3dr-wifi.log.9 100% 78KB 4.3MB/s 00:00

boot 100% 1234 981.3KB/s 00:00

boot.1 100% 1234 473.0KB/s 00:00

boot.10 100% 1234 645.5KB/s 00:00

boot.11 100% 1234 736.6KB/s 00:00

boot.12 100% 1234 656.0KB/s 00:00

boot.13 100% 1234 660.3KB/s 00:00

boot.14 100% 1234 148.3KB/s 00:00

boot.15 100% 1234 607.1KB/s 00:00

boot.16 100% 1234 699.0KB/s 00:00

boot.17 100% 1234 652.5KB/s 00:00

boot.18 100% 1234 661.0KB/s 00:00

boot.19 100% 1234 542.1KB/s 00:00

boot.2 100% 1234 644.8KB/s 00:00

boot.20 100% 1234 654.2KB/s 00:00

boot.3 100% 1234 668.7KB/s 00:00

boot.4 100% 1234 673.2KB/s 00:00

boot.5 100% 1234 634.3KB/s 00:00

boot.6 100% 1234 673.2KB/s 00:00

boot.7 100% 1234 585.6KB/s 00:00

boot.8 100% 1234 591.6KB/s 00:00

boot.9 100% 1234 647.5KB/s 00:00

dmesg 100% 16KB 868.4KB/s 00:00

dmesg.1 100% 16KB 3.0MB/s 00:00

dmesg.10 100% 16KB 2.7MB/s 00:00

dmesg.11 100% 16KB 3.0MB/s 00:00

dmesg.12 100% 16KB 3.0MB/s 00:00

dmesg.13 100% 16KB 2.3MB/s 00:00

dmesg.14 100% 16KB 3.0MB/s 00:00

dmesg.15 100% 16KB 3.1MB/s 00:00

dmesg.16 100% 16KB 1.9MB/s 00:00

dmesg.17 100% 16KB 2.9MB/s 00:00

dmesg.18 100% 16KB 2.9MB/s 00:00

dmesg.19 100% 16KB 2.2MB/s 00:00

dmesg.2 100% 16KB 3.1MB/s 00:00

dmesg.20 100% 16KB 2.9MB/s 00:00

dmesg.3 100% 16KB 3.1MB/s 00:00

dmesg.4 100% 16KB 3.1MB/s 00:00

dmesg.5 100% 16KB 2.7MB/s 00:00

dmesg.6 100% 16KB 2.9MB/s 00:00

dmesg.7 100% 16KB 3.1MB/s 00:00

dmesg.8 100% 16KB 1.5MB/s 00:00

dmesg.9 100% 16KB 3.1MB/s 00:00

kern.log 100% 25KB 3.5MB/s 00:00

kern.log.1 100% 25KB 2.8MB/s 00:00

kern.log.10 100% 25KB 3.4MB/s 00:00

kern.log.11 100% 25KB 3.0MB/s 00:00

kern.log.12 100% 25KB 3.5MB/s 00:00

kern.log.13 100% 25KB 3.3MB/s 00:00

kern.log.14 100% 25KB 3.6MB/s 00:00

kern.log.15 100% 25KB 3.5MB/s 00:00

kern.log.16 100% 25KB 3.3MB/s 00:00

kern.log.17 100% 25KB 2.4MB/s 00:00

kern.log.18 100% 25KB 1.8MB/s 00:00

kern.log.19 100% 25KB 3.5MB/s 00:00

kern.log.2 100% 25KB 1.9MB/s 00:00

kern.log.20 100% 25KB 2.5MB/s 00:00

kern.log.3 100% 25KB 3.4MB/s 00:00

kern.log.4 100% 25KB 3.0MB/s 00:00

kern.log.5 100% 25KB 3.8MB/s 00:00

kern.log.6 100% 25KB 2.8MB/s 00:00

kern.log.7 100% 25KB 2.3MB/s 00:00

kern.log.8 100% 25KB 2.9MB/s 00:00

kern.log.9 100% 25KB 3.8MB/s 00:00

scp: /log/lost+found: not a regular file

messages 100% 3427 1.6MB/s 00:00

messages.1 100% 83KB 3.8MB/s 00:00

messages.10 100% 25KB 3.2MB/s 00:00

messages.11 100% 30KB 3.5MB/s 00:00

messages.12 100% 20KB 2.1MB/s 00:00

messages.13 100% 28KB 3.2MB/s 00:00

messages.14 100% 6646 1.3MB/s 00:00

messages.15 100% 13KB 1.5MB/s 00:00

messages.16 100% 7882 1.8MB/s 00:00

messages.17 100% 47KB 3.6MB/s 00:00

messages.18 100% 6167 1.5MB/s 00:00

messages.19 100% 11KB 2.1MB/s 00:00

messages.2 100% 5444 1.6MB/s 00:00

messages.20 100% 5204 1.1MB/s 00:00

messages.3 100% 13KB 2.1MB/s 00:00

messages.4 100% 2461 1.0MB/s 00:00

messages.5 100% 14KB 2.4MB/s 00:00

messages.6 100% 5454 1.5MB/s 00:00

messages.7 100% 21KB 1.6MB/s 00:00

messages.8 100% 24KB 3.0MB/s 00:00

messages.9 100% 44KB 3.9MB/s 00:00

scp: /log/solo: not a regular file

solo.tlog 100% 9780KB 8.5MB/s 00:01

solo.tlog.1 100% 3886KB 7.6MB/s 00:00

solo.tlog.2 100% 6849KB 7.9MB/s 00:00

solo.tlog.3 100% 919KB 7.0MB/s 00:00

solo.tlog.4 100% 3097KB 7.9MB/s 00:00

solo.tlog.5 100% 509KB 7.2MB/s 00:00

solo.tlog.6 100% 3971KB 8.2MB/s 00:00

solo.tlog.7 100% 91KB 4.1MB/s 00:00

solo.tlog.8 100% 3483KB 7.8MB/s 00:00

solo.tlog.9 100% 435KB 7.4MB/s 00:00

scp: /log/updates: not a regular file

wtmp 100% 6912 2.6MB/s 00:00

wtmp.1 100% 20KB 2.6MB/s 00:00

wtmp.10 100% 20KB 2.6MB/s 00:00

wtmp.11 100% 20KB 2.2MB/s 00:00

wtmp.12 100% 20KB 2.6MB/s 00:00

wtmp.13 100% 20KB 3.2MB/s 00:00

wtmp.14 100% 20KB 2.6MB/s 00:00

wtmp.15 100% 20KB 2.8MB/s 00:00

wtmp.16 100% 20KB 2.6MB/s 00:00

wtmp.17 100% 20KB 2.7MB/s 00:00

wtmp.18 100% 20KB 2.0MB/s 00:00

wtmp.19 100% 20KB 2.3MB/s 00:00

wtmp.2 100% 20KB 2.3MB/s 00:00

wtmp.20 100% 20KB 2.8MB/s 00:00

wtmp.3 100% 20KB 3.3MB/s 00:00

wtmp.4 100% 11KB 2.2MB/s 00:00

wtmp.5 100% 20KB 2.3MB/s 00:00

wtmp.6 100% 20KB 2.6MB/s 00:00

wtmp.7 100% 20KB 2.5MB/s 00:00

wtmp.8 100% 20KB 3.2MB/s 00:00

wtmp.9 100% 20KB 2.6MB/s 00:00

 

[DJMc]

Thats a fantastic gadget - thanks for the lead. (Was that your video? That water descent and the sound of the go pro going under water is unnerving)

This is a good reason why I have the Solo set to Return to me VS Return from take off. If there are others who are not aware of this feature, its very handy if you move around while controlling the solo (like a "follow me" smart shot), so it goes back to where the controller is (with you) vs. where you originally took off.

Thanks again, @skyhax I'm definitely getting that for the next one.

If you're using the original 3DR Android app rather than vastly superior third party Solex app, then you might want to review the 'Return to Me' bug discussed in the thread below;

https://3drpilots.com/index.php?threads/9244/

 

[Pedals2Paddles]

One of the first few tlog files.

 

[andrew.baker.142]

Very sorry to hear about that. Wish you had one of these onboard:
https://tinyurl.com/y9nf43oy

Worked here:

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

I fly with a "Getterback" on one of my Solo legs whenever I'm planning on flying over water. Only weighs 11g and will at least allow me to recover the GoPro (with extended warranty) and onboard video.
I just came back from a wonderful vacation in Nova Scotia where I flew over salt water extensively. The real risk was the water temperature was probably in the 50's so without a boat I probably wouldn't be swimming very far out to recover the aircraft without a wetsuit.
I'll post some videos once a do a little editing.

 

[Travelfox]

I fly with a "Getterback" on one of my Solo legs whenever I'm planning on flying over water. Only weighs 11g and will at least allow me to recover the GoPro (with extended warranty) and onboard video.
I just came back from a wonderful vacation in Nova Scotia where I flew over salt water extensively. The real risk was the water temperature was probably in the 50's so without a boat I probably wouldn't be swimming very far out to recover the aircraft without a wetsuit.
I'll post some videos once a do a little editing.

Great! I Moved to Nova Scotia from Vancouver. There's more than a hundred and fifty lighthouses here and we have one at the end of the road where I was flying and that's where I lost my drone to the water. Too bad I didn't know about this or I'd definitely have at least one.