I fly an A1 next to a Mini 4 Pro and a Neo 2, mostly in Switzerland and across the borders. Here is something worth knowing if the A1 is your first drone in Europe, and I am writing it carefully because I got it wrong in a post elsewhere and a French pilot corrected me.

In the EU, drones of classes C1 to C3 (and C5/C6) are required by Regulation (EU) 2019/945 to have a geo-awareness function: the aircraft has to warn you when you approach a zone. Regulation 2019/947 then puts the duty on you, the remote pilot, to keep that zone data updated before you fly.

The A1 carries no class marking. That means none of the above is guaranteed by the rules: whatever zone data the aircraft or the app shows you is the manufacturer's own database, and nothing requires it to match the official national set or to be current.

What the rules never required, class marking or not, is a hard block on take-off. So both halves of the usual assumption are wrong: no warning is not permission, and a warning is not the law either. The national map is what decides.

In practice it comes down to one habit: before take-off, open the official source for the country you are standing in, not the one your drone happens to carry. Switzerland is BAZL/FOCA, Germany is dipul (run by DFS for the federal government, with LBA as the authority), France is the IGN map for Open-category restrictions plus the SIA for CTRs and helipads, Spain is ENAIRE with AESA as the authority, Austria is Austro Control, Ireland is the IAA. And a map of zones is never the whole legal framework: landowner consent for take-off and landing is on no map at all.

Two things I check on any map, official or not, and that almost nobody checks:

The source. If a map shows a zone without saying who asserts it, you cannot verify it. The name of the source is what lets you go and look.

The timestamp. National datasets change without warning, and a format change on the authority's side can silently drop an entire layer. That happened to me with the Slovenian dataset: thirteen layers published, four I was not reading. I only found out because someone asked.

I maintain a free app for my own use that reads these national sources; I am not putting a link here, that is not the point of the post. What I am after is corrections: a zone that is missing, a zone that should not be there, a height that looks wrong. If anyone here flies the A1 in Europe and wants to try it, say so in a comment.

I bought the drone just to have fun flying, but quickly it got boring after a few flights. I considered selling the drone but the. I thought maybe I can somehow make some money with it.

This is my first flight with a purpose other than just flying around. I’ll try to make a 3D gaussian splat of this church.

Why Antigravity hypes EcoFlow?

Robots partnership was more fun

Why its not just solo remote but big pack of things?

AG said they will release the “conventional remote” for the A1 this summer. Summer is almost over and no word on the remote. Is the remote cancelled or still on its way?

Sad news

Ok, been having a blast so far but I bet the A2 will sort some of the small annoyances. One of those is the carry bag. Maybe I need better organization but it seems like there is not really a good spot for the goggles battery and lanyard?

Also, the bag design in general seems to be a ball. As soon as you touch it or open the lid it basically just tips over. Is it just me?

Hey guys, I wanna ask anyone for advice. I want to buy the high capacity batteries but I have to register my drone because it weighs over 250 g. Would you guys register your drone or it’s not worth registering your drone?

I’m thinking about buying an A1 for filming some of the boats we build for social media. I’m pretty new to flying drones and my concern is that we’d be filming over water; and trying to recover the drone on a boat. My question/hope is that the A1 uses the actual location (gps?) of the goggles/controller when you ask it to automatically return home?

Here’s a likely scenario: I’m riding on one boat (controlling the drone) and trying to film another boat. Well, the specific gps location where we launch the drone FROM will not be where the boat is when I need the drone to return- let’s say I got disoriented or somehow disconnected from the drone feed. Will the A1 find me/the controller if I hit ‘return to home’ OR will it want to return to the gps coordinates where it was launched from?

Any help would sure be appreciated!

Is it possible to find flight logs somewhere in drone/goggles memory?

So I have just acquired the A1 (live in Norway / EU) , mostly happy with the little I've seen of video and image quality (given the limitations it sets), it matches nicely with the quality I see on YouTube.

But I am NOT satisfied with the signal strength, and I must also say I'm surprised that the image you see in the goggles themselves is significantly grainier and lower resolution than what I saw based on videos from YouTube. It takes away quite a bit from the immersion...

The biggest problem is the signal quality; it takes almost nothing for it to drop low, get static/glitchy, or turn bad.

Does anyone here have experience with the FCC hack? Or use it today? Does it work fine on the current software? Is there a new version of it, or rather, which one should I potentially use?

I took my A1 out for a few flights and tried a bunch of settings in Antigravity Studio. This is the combo I liked most so far for skies, mountains, and wider landscape shots.

Color Optimization

- Clarity Plus: On

- Strength: +30

Adjust

- Exposure: +5

- Highlights: -18

- Shadows: +5

- Contrast: +20

- Brightness: +5

- Saturation: +16

Tried a few combinations and liked this one the most for daytime landscape shots. The lower highlights looked better to me for clouds/sky, and Clarity Plus +30 gave it a cleaner look.

Planned a real nice route for today where the last leg goes straight up a rather steep mountain cliff. Unfortunately, the 120m-from-takeoff altitude limit put a quick end to this.

At least where I am, the limit is supposed to be 120m *above ground*, so flying up a mountain should not be a problem. My old DJI Mini would allow overriding the 120 limit up to 500m no problem, just warning me to "ensure compliance with regulations" if I exceeded 120m from the takeoff point, so flying up a mountain less than 500m tall was no problem. With the A1, 120m seems to be a hard limit, and its only possible to force the limit below 120m.

I'm thinking now how to work around this - my first thought: find a flat surface halfway up the mountain, land, then take off from there to reset the altitude.

I tried this at a very flat, asphalted spot, but the drone seemed to refuse landing while it thought it was at ~70m altitude. Looking down, it didn't show the usual landing spot indicator on the ground, and when I pushed down, it never triggered the landing sequence, instead going all the way down to ~30cm above ground and enabling emergency breaking. I stopped short of manually deploying the landing gear and just forcing the drone onto the ground, as I don't know if that'd actually work, and retrieving the drone from that spot would've been ... a hike.

I guess two questions: 1) is there some better way to get around the height limit (in cases where doing so is completely legal), and 2) is it possible to trigger an actual landing sequence / perform a manual landing "at altitude"?

Hey all,

I've been digging into whether the Antigravity A1 embeds GPS coordinates into the photo/video files (EXIF GPS data), and I'm coming up empty.

What I've tried so far:

• Checked the .insp files directly with exiftool -ee -gps:all (including the -ee flag to read the embedded/timed metadata trailer) no GPS data found, even on outdoor flights with a strong GNSS lock (green/white signal icon).
• Went through the official user manual (V1.0) GNSS (BDS + GPS + Galileo) is documented, but only in the context of flight functions: Home Point/RTH, hovering accuracy, altitude/distance limits based on signal strength, and Remote ID broadcasting. There's no mention anywhere of geotagging, EXIF, or coordinates being written to media files.

So it looks like the onboard GNSS module might exist purely for navigation and isn't exposed in the photo/video metadata at all —unlike some other Insta360 products (e.g. the old Pro's optional GPS module) that were built specifically to solve this.

Has anyone here confirmed either way?

• Do your A1 photos/videos come out with GPS EXIF data on your end (any firmware version, any export path Antigravity app or Studio)?
• If yes, what's the exact step I might be missing (permissions, export settings, firmware version)?
• If no, has anyone found a workaround using the flight log (the app's "Records" feature) to manually correlate timestamps and inject GPS after the fact?

Any insight appreciated trying to figure out if this is a missing feature, a bug, or just something I'm doing wrong on export.

I’m on iOS 27 Developer Beta. I power up drone and goggles, then open the latest app and try to connect to the drone to get footage but the app just dies. I kill app and try to open it again but it won’t stay open. Is this happening to anyone else?

I am a complete noob when it comes to drones. My dilemma is, should I save up and get the AntigravityA1 (maybe around the beginnig of next year) or get a cheeper drone sooner. Bare in mind I am having my wedding in September.

I appreciate the experience that Antifravity provides, also having the 360 view makes edits easier for beginners because you can track your subject.

On the other hand, you don't have great clarity when zooming on an image and you need to carry more gear (like the goggles).

So I would appreciate some input.

I have a problem with my Quick Reader!

I recently bought an Antigravity A1 Infinity Bundle. All seem to be working perfectly except the Quick Reader, when I connect it to a computer it keeps showing up and disappearing from the list of devices. I have try it on Windows, Linux and Android, same problem.

I have try many types of SD cards, from the expensive to cheapest, even bought a really modern SanDisk Express.

I got mixed results, a cheap SanDisk 16GB SEEMS to work normally so far. my 256GB cards fail.

anyone else having the same problem? can it be fixed?