I can’t lie - a few times today, whilst walking through sodden fields, I’ve thought the same. But I am sure DJI wouldn’t honour that claim. There’s Fly Away, then there’s Chuck It Away.
Won’t know unless you try 
2 Likes
You are covered no matter what
Flyaway replacement fee: GBP209
- Flyaway
If you decide to use the flyaway replacement service, accident flight records need to be provided, and a DJI Care Flyaway Aircraft Report should be produced as a certificate for the replacement service. If accident flight records cannot be provided or a DJI Care Flyaway Aircraft Report is not produced, DJI reserves the right to reject the application for the flyaway replacement service.
Data analysis will not be performed during the replacement service process.
After a DJI Care Flyaway Aircraft Report is produced, the flyaway aircraft will be restricted from use. If the aircraft is found before paying the service fee, you can contact DJI to cancel the DJI Care Flyaway Aircraft Report, and then your product can be used normally again. If you have already paid the service fee, the ownership of your original product will be transferred to DJI as a certificate of the replacement service and the DJI Care Flyaway Aircraft Report cannot be cancelled.
Is there a time limit to report it?
Apologies, thought it was a natural shift in the conversation but see your point 
No, not from what I can see, the only stipulation is it is bound to the controller before the fly away
1 Like
Spot on …
1 Like
Been looking, but everything from that time looks like this … i.e. no lat/lng’s, or anything helpful.
Good shout though 
Cheers Wayne. Good to know. If all else fails, it may indeed come to that.
Yes, it is bound to the RC.
Well … I will attempt SAR #3, and if that leads to nothing, I will probably (a) do what you suggest, or (b) take up knitting again
1 Like
Just been looking at the flight path with Google earth for some clues but not much help for what I can see
A GADC bobble hat 
That top image really shows the elevation, which is what I think determines ‘which’ field it is in. So thanks for that. To me, it supports @ximi’s model, which shows it landing (crashing) in the NE field
If those are the .txt files, upload them to AirData manually from the web page.
If you download the .csv files from AirData, and open in Excel, it includes AirData’s calculation of height above ground.
The last-but-one point, before the satellites all but vanished, gives…
| datetime(utc) | latitude | longitude | height_above_takeoff(feet) | height_above_ground_at_drone_location(feet) |
|---|---|---|---|---|
| 18/02/2022 10:42:28 | 51.49564961 | -1.782977296 | -45.275592 | 222.7034192 |
2 Likes
I was excited for 4 seconds.
1 Like
Nope - AirData needs the .txt log files.
1 Like
That’s close to the 222ft in the AirData .csv data … 68m = 223ft.
There are no txt log files from after the ‘incident’, just zip files and log files. And the zips, will not open, with any means.
In Android, they used to be located in DJI>DJI.GO.V4>FLIGHTRECORD.
But someone was saying that recently the Fly App located them within …
Android>Data>dji.xxxx somewhere.
Ah … that’s a shame.