What this app is for:
I'm a backcountry pilot, and I'm always scouting for new off-field places to land: a dry lakebed,
a ridge-top strip, a two-track along a creek. There are apps that show where it's legal to ride a dirt bike,
but nothing built for pilots. So I made OffField: a map that shows who owns or manages the land under you,
what the rules say about landing there, and the strips other pilots know about, so backcountry pilots can
find, save and share great places to land.
It can be wrong. Land records, boundaries and laws change, and the app's verdicts are a starting
point, not an answer. Always do your own research on legality, and get permission, before you land.
Chase · chase@cffly.org
How it works:
What it shows: Press and hold any spot to see the parcel there and who owns it, who manages the land
(BLM, Forest Service, a state agency…), whether it's wilderness, the airspace and nearby airports,
and a landing verdict ("Legal", "Permission required", "Not allowed", "Unclear") with a
confidence level and the sources behind it.
Where the data comes from: County and state parcel maps; a paid owner-lookup service where
counties don't publish owners; the BLM's land-manager map, Wilderness Connect, BLM Wilderness Study
Areas and the USGS Protected Areas Database; FAA airports, airspace, charts and the Digital Obstacle
File and TFRs; aviationweather.gov weather reports; NIFC fire perimeters; BLM National Monuments,
Conservation Areas and ACECs; BLM field offices; Forest Service ranger districts; state land agency websites; AWS terrain tiles (elevation); federal transmission-line
maps; Census boundaries; FAA runways; airstrips mapped in OpenStreetMap (© OpenStreetMap contributors, ODbL);
OpenStreetMap and Esri base maps.
How it judges landing legality: It combines federal rules (FAA, BLM, Forest Service,
National Parks, wildlife refuges, wilderness, military land) with each covered state's own laws,
researched from the statutes and regulations and dated when last reviewed. Where the law doesn't
clearly address landing, it says "Unclear" and may list pilot reports, labeled as experience, not law.
Pilot reports: a report you send (date, aircraft, surface, notes and an optional photo, with the
strip or spot it's about) is stored on CFfly's server and shown to everyone using OffField with your callsign
(not your name). Your IP address is used, hashed, only to limit how many reports can be sent. Reports are pilots'
experience, not law, can be wrong, and never change the landing verdict. Report anything wrong or
inappropriate with "Report this".
Private and public spots: spots you save are private: only you see them. If you choose "Make it public",
a copy (location, name, surface, use, notes and photos) is reviewed by CFfly and, if approved, shown to everyone
using OffField as a pilot-submitted strip or spot, without your name, where pilots can add reports. You can
withdraw it at any time. A listed strip or spot is never permission to land.
Accounts: if you sign in with Google or Apple, CFfly's server keeps your name, email (Apple may give a
private relay address), which service you used, when you last signed in and how many owner lookups you've used
this month, so CFfly can decide who may use the paid owner lookups. Nothing else from your Google or Apple
account is used. While you're signed in, your saved spots (with their notes, photos and permission records) and
your settings (including your pilot details) are also kept in your account on CFfly's server, privately, so they
reach your other devices; only you can see them. You can sign out, or delete the account (Profile (people button → Profile)), at any time; deleting it removes
these records and your synced spots, photos and settings from the server (spots stay on your devices), and
your pilot reports stay without your name.
Wingmen and squadrons: if you use them, CFfly's server also keeps your callsign, and the name, email and
phone from your pilot details, whether and how you allow other pilots to find you, your wingmen and squadrons, the squadron spots you add and
what you send to wingmen and squadrons (spots, strips, trip reports with their tracks, notes and photos). Other
pilots see only your callsign (or first name), never your email or phone. Squadron spots are seen only by
that squadron's members. Deleting your account removes your wingmen, the squadrons you own (with their spots and
posts) and what you sent or were sent; spots you added to others' squadrons stay, without your name.
Your data: When you aren't signed in, saved spots (with notes, photos and permission records) and your
pilot details (name, phone, email, aircraft and N-number, entered in Settings for permission letters) are kept
only on this device. They aren't sent anywhere unless you share a link, export a file or send a permission letter
yourself, so sign in or back them up (Settings → Backup). Recorded flights (the logbook: tracks, landings, notes
and photos) stay on this device unless you share one as a trip report.
The fine print:
No promises: The data can be outdated, incomplete or wrong; boundaries are approximate
(offline data is simplified to about 100 m); the strip check's terrain, weather, obstacle and power-line
data is for screening only and misses many hazards (wires, fences, rough surfaces), and "Find strips"
results are terrain-based candidates, not surveyed or approved landing sites; laws change; city and county rules aren't covered.
This is general guidance, not legal advice and not for navigation. You, the pilot in
command, are solely responsible for the safety and legality of every flight: get the landowner's or
agency's permission, and check NOTAMs, TFRs and current charts. The app is provided as-is, without
warranty of any kind, and CFfly accepts no liability for how it's used.
Please scroll to the bottom and read it all first.