Part of what follows was totally my fault - which I want to share to avoid others making the same mistake - and part of it, I discovered through trial and error, and it also may be useful to know.
I was pre-planning a flight with my Mavic Air 2 yesterday. This flight was going to be in the area of a Class D airport not currently supported by LAANC, and I have an FAA Airspace Authorization for the airspace at or below the altitudes listed in the airport's UAS Facility Map.
Parts of this airspace are also listed as an Authorization Zone in DJI's NFZ database, so I went into the FlySafe website on my PC in order to unlock this airspace prior to this flight. I logged in, selected 'Self Unlocking', selected the area of airspace on the map, and then I made my first error. I entered my Remote Controller S/N into the form, and after going through the next steps, I got the confirmation that I was all set. When I went flying however, I was still locked out of the airspace, and although when I went into the Unlocked GeoZones portion of the Fly App, it showed that I had a valid Authorization for the airspace, on the right, it showed 'Aircraft Disconnected'. I logged out and back into the Fly App, I deleted and reinstalled the app, and I finally gave up when nothing seemed to work.
Back home, I again attempted to unlock this airspace via FlySafe on my PC, and after doing so, I now had two Authorizations showing in the Fly App. Then, I took a closer look at the application form. The S/N requested is that of the Flight Controller which is a module on the aircraft itself - and its S/N can be found in the 'About' section of the Fly App where the RC's S/N is also listed, as long as the copter is on and connected to the RC.
So, I went through the process again using the Flight Controller S/N, and although it eventually showed up as a valid Authorization, it - like the other two still listed - showed Aircraft Disconnected' on the right. What I did next was to delete all three Authorizations from the Fly App, followed by one final application in FlySafe using the Flight Controller S/N, and this one showed up right away with the icon on the right showing Import to Aircraft - or something similar. Problem solved.
So, it is the Flight Controller S/N that the form requires, and if there are Authorizations showing in the Fly App that are linked to your account but still have errors in them, delete them from the Fly App prior to going any further.
Hopefully this will save somebody from the frustrations that I experienced...
I was pre-planning a flight with my Mavic Air 2 yesterday. This flight was going to be in the area of a Class D airport not currently supported by LAANC, and I have an FAA Airspace Authorization for the airspace at or below the altitudes listed in the airport's UAS Facility Map.
Parts of this airspace are also listed as an Authorization Zone in DJI's NFZ database, so I went into the FlySafe website on my PC in order to unlock this airspace prior to this flight. I logged in, selected 'Self Unlocking', selected the area of airspace on the map, and then I made my first error. I entered my Remote Controller S/N into the form, and after going through the next steps, I got the confirmation that I was all set. When I went flying however, I was still locked out of the airspace, and although when I went into the Unlocked GeoZones portion of the Fly App, it showed that I had a valid Authorization for the airspace, on the right, it showed 'Aircraft Disconnected'. I logged out and back into the Fly App, I deleted and reinstalled the app, and I finally gave up when nothing seemed to work.
Back home, I again attempted to unlock this airspace via FlySafe on my PC, and after doing so, I now had two Authorizations showing in the Fly App. Then, I took a closer look at the application form. The S/N requested is that of the Flight Controller which is a module on the aircraft itself - and its S/N can be found in the 'About' section of the Fly App where the RC's S/N is also listed, as long as the copter is on and connected to the RC.
So, I went through the process again using the Flight Controller S/N, and although it eventually showed up as a valid Authorization, it - like the other two still listed - showed Aircraft Disconnected' on the right. What I did next was to delete all three Authorizations from the Fly App, followed by one final application in FlySafe using the Flight Controller S/N, and this one showed up right away with the icon on the right showing Import to Aircraft - or something similar. Problem solved.
So, it is the Flight Controller S/N that the form requires, and if there are Authorizations showing in the Fly App that are linked to your account but still have errors in them, delete them from the Fly App prior to going any further.
Hopefully this will save somebody from the frustrations that I experienced...
Last edited: