37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1721078 |
Time | |
Date | 202001 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | RNO.Tower |
State Reference | NV |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | UAV - Unpiloted Aerial Vehicle |
Operating Under FAR Part | Other Part 107 |
Flight Phase | Cruise |
Person 1 | |
Function | Pilot Flying |
Events | |
Anomaly | Airspace Violation All Types Deviation - Procedural Published Material / Policy Deviation - Procedural FAR |
Narrative:
I the rpic (remote pilot in charge) called tower per the instructions to inform them about the uas operation that would be taking place within the next fifteen minutes at the location. Tower acknowledged the request and the rpic conducted the mission. The rpic called tower at the conclusion of the operation. Tower acknowledged the message and the rpic wrapped up for the night. Six days later the rpic realized that he had flown outside of the certificate of authorization (coa) by flying a day earlier than what was specified in the coa (certificate of approval).the rpic received a request to fly the class C 0' grid area (per the FAA uas FM) so he determined that filing through drone zone with night operations included would be the fastest way to acquire the approval. Rpic advised the FAA representative; about his intentions for adding night operations was to be able to gain approval faster. The approval came in and the rpic thought the timing was perfect and did not check the authorization start date on the authorization itself. He made the error because he was eager to be able to fly that area.the rpic wanted to get the photos by deadline. The operator was excited to have the coa in hand. The operator expected the start date to be the same date as requested but the FAA changed the date to be the day after only on the coa but it was still shown as the requested date on drone zone. Drone zone shows the approved start date as one date and also shows that the modified approved end date was changed to three days later.
Original NASA ASRS Text
Title: A UAS pilot operated their drone on a different day than what was approved by the FAA.
Narrative: I the RPIC (Remote Pilot in Charge) called Tower per the instructions to inform them about the UAS operation that would be taking place within the next fifteen minutes at the location. Tower acknowledged the request and the RPIC conducted the mission. The RPIC called Tower at the conclusion of the operation. Tower acknowledged the message and the RPIC wrapped up for the night. Six days later the RPIC realized that he had flown outside of the Certificate of Authorization (COA) by flying a day earlier than what was specified in the COA (Certificate of Approval).The RPIC received a request to fly the Class C 0' Grid Area (Per the FAA UAS FM) so he determined that filing through Drone Zone with night operations included would be the fastest way to acquire the approval. RPIC advised the FAA representative; about his intentions for adding night operations was to be able to gain approval faster. The approval came in and the RPIC thought the timing was perfect and did not check the authorization start date on the authorization itself. He made the error because he was eager to be able to fly that area.The RPIC wanted to get the photos by deadline. The Operator was excited to have the COA in hand. The Operator expected the start date to be the same date as requested but the FAA changed the date to be the day after only on the COA but it was still shown as the requested date on Drone Zone. Drone Zone shows the Approved Start Date as one date and also shows that the modified Approved End Date was changed to three days later.
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.