Uav operator reported operating within the borders of class east airspace.

Attributes
ACN	1477824
Time
Date	201708
Local Time Of Day	0601-1200
Place
Locale Reference	APG.Airport
State Reference	MD
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	UAV - Unpiloted Aerial Vehicle
Operating Under FAR Part	Other 107
Flight Phase	Other All Phases
Route In Use	None
Flight Plan	None
Person 1
Function	Single Pilot
Qualification	Flight Crew Multiengine Flight Crew Instrument Flight Crew Commercial
Experience	Flight Crew Last 90 Days 4 Flight Crew Total 554 Flight Crew Type 4
Events
Anomaly	Airspace Violation All Types Deviation - Procedural FAR Deviation - Procedural Published Material / Policy

Narrative:

I operated a mavic pro uav as rpic (remote PIC) accidentally within the border of the class east airspace to the surface approach path into philips aaf (apg). The problem arose due to airspace inspection that was not detailed enough. Due to my distance from controlled airports; I believed I was in class G airspace; however; further detailed inspection of the airspace after landing the uav showed that I was actually operating within the edge of the class east airspace approach path. It was my understanding that two other people had confirmed that the area I operated the uav in was class G airspace; however they had either not done an airspace inspection or had done an incomplete airspace inspection resulting in the wrong airspace identified. As rpic; it was my error in not double checking their airspace identification before operating the uav. No conflicts with other aircraft occurred with this violation.

Original NASA ASRS Text

Title: UAV operator reported operating within the borders of Class E airspace.

Narrative: I operated a Mavic Pro UAV as RPIC (Remote PIC) accidentally within the border of the Class E airspace to the surface approach path into Philips AAF (APG). The problem arose due to airspace inspection that was not detailed enough. Due to my distance from controlled airports; I believed I was in Class G airspace; however; further detailed inspection of the airspace after landing the UAV showed that I was actually operating within the edge of the Class E airspace approach path. It was my understanding that two other people had confirmed that the area I operated the UAV in was Class G airspace; however they had either not done an airspace inspection or had done an incomplete airspace inspection resulting in the wrong airspace identified. As RPIC; it was my error in not double checking their airspace identification before operating the UAV. No conflicts with other aircraft occurred with this violation.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.