Drone No-Fly Alerts - New FAA TFRs Near Your Locations
Pricing
from $2.00 / 1,000 tfrs
Drone No-Fly Alerts - New FAA TFRs Near Your Locations
Flying a drone job next week? Give it your job sites (lat/lng + radius) and get an alert the moment a NEW FAA Temporary Flight Restriction (VIP, stadium, hazard, security) touches one. Reads the official FAA TFR list and geometry; each TFR is reported once.
Pricing
from $2.00 / 1,000 tfrs
Rating
0.0
(0)
Developer
mohamed alaya
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a month ago
Last modified
Categories
Security
Limited permissionsShare
Get told when a new FAA Temporary Flight Restriction (TFR) touches one of your drone job sites. Built for drone service companies, Part 107 pilots and event or film crews who need to know before they fly.
It reads the FAA's official active TFR list and each TFR's published geometry, remembers what it already told you, and flags only the new TFRs that cover (or come near) your points.
Quick start - three copy-paste inputs
Demo (empty input works):
Two job sites with their own radius:
Only VIP and security TFRs in Florida and Texas, with a Slack webhook:
Schedule it hourly or daily with the same stateStoreName and you get an alert only for TFRs you have not seen.
Input guide
| Field | What it does |
|---|---|
locations | Your points: objects {name, lat, lng, radiusMiles} or plain "lat,lng" text. |
radiusMiles | A TFR touches a point when its boundary is within this many miles (0 = point must be inside). |
tfrTypes, states | Optional filters (VIP, SECURITY, HAZARDS, SPACE OPERATIONS, AIR SHOWS/SPORTS, UAS PUBLIC GATHERING ...). |
outputMode | all-new = a row for every new TFR plus every hit; hits-only = only TFRs that touch your points. |
maxBaselineRows | On the first run every active TFR looks new; at most this many TFR rows are listed (marked isBaseline). Hits are still checked for all of them. |
stateStoreName | Named memory store. Same name on every scheduled run. |
webhookUrl | Optional POST of new hits (Slack, Discord, Zapier, Make). |
Output
| Field | Meaning |
|---|---|
type | tfr, geofence-hit, error or run-summary |
notamId, tfrType, state | FAA NOTAM number, type and state |
location, distanceMiles, inside | (hit rows) your point and how far the TFR boundary is (0 = inside) |
effectiveFrom, effectiveUntil, activeNow | Schedule in UTC; effectiveUntil null means no end date published |
floorFt, ceilingFt | Altitude limits from the FAA data |
url | The FAA's TFR detail file (XML) |
Sample hit row:
Use it with
- Schedule + webhook to Slack for a daily "any new TFR near my jobs" ping.
- Feed
geofence-hitrows into your dispatch sheet or CRM through Make or Zapier.
FAQ
Is this the legal source? It uses the FAA's public TFR data (tfr.faa.gov). Always confirm in the FAA's own tools and your flight planning app before you fly. This Actor is an alerting aid, not flight clearance.
Does it cover LAANC, NOTAMs other than TFRs, or controlled airspace? No. TFRs only.
Why are some TFRs permanent? Theme parks and similar sites have long-running TFRs; they have no end date.
Honest limits
- Polygon edges are used as published (circles are already sampled into polygons by the FAA). Distances are approximate (flat-earth math, good to a fraction of a mile).
- A TFR is reported once, by NOTAM number. A later amendment of the same NOTAM is not re-reported.
- If the FAA's geometry file for a TFR cannot be read, that TFR is retried on the next run and an
errorrow says so.
Price
Pay per event: $0.002 per new TFR row, $0.01 per geofence hit. A daily run with two job sites that sees 8 new TFRs and 1 hit costs about $0.026.
