Skip to content
View in the app

A better way to browse. Learn more.

The Drone Talk Hub - The Ultimate Drone Community Hub

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

FAA-Recognized Identification Areas (FRIA)

FAA ACS — Task I.F: Remote Identification (RID)

Lessons B and C covered the two equipment-based ways to comply with Remote ID. This lesson covers the one scenario where no Remote ID equipment is required at all: operating entirely within an FAA-Recognized Identification Area, or FRIA. This lesson explains what a FRIA is, who is eligible to establish one, how the FAA evaluates and approves an application, and the operating limits — VLOS and staying within the boundary — that apply once you are flying inside one.

Subpart C§§ 89.201–89.230
CBO or schoolEligible applicants
48 monthsApproval duration
VLOSRequired inside a FRIA

The only way to fly without any Remote ID equipment

An FAA-Recognized Identification Area is a defined geographic area, formally approved by the FAA, within which an unmanned aircraft may be operated without Standard Remote ID, without a broadcast module, and without broadcasting any Remote ID message elements at all. It is the single exception in Part 89 to the general rule that a registered (or required-to-be-registered) aircraft must comply with § 89.105 through one of the two equipment-based methods in Lessons B and C. Operating inside an approved FRIA is itself the compliance method — the location substitutes for the equipment.

This matters most for older aircraft that cannot be retrofitted with a broadcast module, home-built aircraft, or hobbyist and educational flying where equipping every aircraft with Remote ID is impractical. It does not, however, exempt the aircraft from registration under Part 47 or Part 48 where that requirement otherwise applies — registration and Remote ID equipage are two separate requirements, and a FRIA only removes the second one.

Who is eligible to establish a FRIA under 14 CFR 89.205

A FRIA cannot be requested by an individual remote pilot or an ordinary business. Section 89.205 limits eligibility to two categories of applicant:

  • A community-based organization recognized by the Administrator: an organization the FAA has separately recognized as meeting its safety-program criteria, such as an established model aviation or drone club.
  • An educational institution: primary and secondary schools, trade schools, colleges, and universities.

A flying club that is not an FAA-recognized community-based organization, or a private company wanting a company-only flying zone, does not qualify under § 89.205 to apply on its own.

Applying for and receiving FRIA approval

An eligible applicant submits a request for establishment under § 89.210, providing the organization's identity, an authorized representative and contact details, the physical location being requested, a statement of purpose, and any existing agreements relevant to the proposed site. The FAA then evaluates the request under § 89.215, considering airspace restrictions affecting the area, the safety impact on other aircraft operating nearby, ground safety and security at the site, and how close the proposed area is to any existing FRIA. Only after the FAA approves the request does the area become an operating FRIA.

14 CFR 89.201–89.230 (Part 89, Subpart C) — Applicability, Eligibility, Requests for Establishment, Approval, Amendment, Duration, Expiration and Termination

Duration, renewal, and changes to an existing FRIA

An approved FRIA is valid for 48 calendar months from its approval date, under § 89.225. To keep it active past that point, the organization must submit a renewal request no later than 120 days before the FRIA expires; missing that window risks a lapse in the area's approved status. If the organization wants to change something about the FRIA — and especially if it wants to change the geographic boundary — § 89.220 requires notifying the FAA within 10 calendar days of the change, and any boundary modification specifically requires FAA approval before it takes effect. Section 89.230 covers how a FRIA can end: automatic expiration if not renewed, a voluntary request from the organization to terminate it, or FAA-initiated termination if the area no longer meets safety or security standards or the organization becomes ineligible, with a 30-day window for the organization to petition for reconsideration.

Operating requirements once inside an approved FRIA

Being inside a FRIA does not remove every other Part 107 or Part 89 requirement — it removes only the Remote ID equipment/broadcast requirement. Two operating limits apply specifically because no equipment is broadcasting the aircraft's location to outside observers: both the unmanned aircraft and the person operating it must remain within the FRIA's approved geographic boundaries for the entire operation, and the operation must be conducted within visual line of sight. A pilot cannot fly a non-equipped aircraft out past the FRIA's edge "just for a moment," and cannot use the FRIA exception to justify a BVLOS flight; both conditions exist precisely because there is no Remote ID broadcast providing outside identification once the aircraft or pilot leaves the approved, contained area.

Aerial-view diagram of a large open field enclosed by a dashed boundary line labeled FAA-Recognized Identification Area (FRIA) Boundary, with a small quadcopter drone and a person holding a controller both shown well inside the boundary, connected by a short dotted line of sight labeled VLOS Required. Outside the boundary, a red X icon marks a point past the dashed line labeled Aircraft and Pilot Must Stay Within FRIA Boundary At All Times, No Remote ID Equipment Required Inside. White background, © DroneTalk lower right.

Both the aircraft and the pilot must remain within an approved FRIA's boundary, and the operation must stay within visual line of sight.

View Larger

Scenario: keeping older, non-equipped club aircraft flying legally

A local model aviation club, already recognized by the FAA as a community-based organization, has members who fly a mix of older fixed-wing aircraft that were never built with Standard Remote ID and are too small or fragile to retrofit with a broadcast module. The club applies under § 89.210 to establish a FRIA at its existing flying field, providing its organizational details, the field's location, and its purpose. The FAA evaluates the request under § 89.215 — checking the airspace around the field, safety impact on other nearby aircraft, ground security at the site, and proximity to any other FRIA — and approves it. For the next 48 months, club members can fly their older aircraft at that specific field, within its boundary and within VLOS, without adding Remote ID equipment to each aircraft. The same members flying those same aircraft at a different field outside the approved boundary would not be covered, and would need Standard Remote ID or a broadcast module instead.

Illustrative diagram of a laptop screen displaying a stylized map interface labeled FAA FRIA Locator with several shaded polygon areas scattered across the map, one shaded area highlighted and selected showing a callout info box reading Status: Approved, Expires: 48 Months From Approval, Type: Community-Based Organization; a magnifying-glass search icon is shown over the map, and a caption below reads Verify a FRIA is currently approved before relying on it. White background, © DroneTalk lower right.

Always verify a FRIA's current approval status before flying without Remote ID equipment; approvals expire after 48 months if not renewed.

View Larger

Finding and Verifying a FRIA Before You Fly Without Remote ID Equipment

Never assume an area is an approved FRIA just because it looks like a dedicated flying field.

1

Check the FAA's official Remote ID resources for current FRIA locations

The FAA maintains official information and a public locator for approved FRIAs. Confirm the specific site is currently approved before relying on it, rather than assuming based on reputation or past experience.

Tip: approvals last only 48 months; a location that was a FRIA in the past may have lapsed if it was not renewed.
2

Confirm the exact boundary of the approved area

Identify the FRIA's actual geographic boundary before flying, since both the aircraft and the pilot must remain inside it for the entire operation.

3

Plan the flight to stay within VLOS the entire time

Position yourself so you can maintain visual line of sight with the aircraft throughout the flight, consistent with the VLOS requirement that applies inside a FRIA.

Caution: flying an unequipped aircraft outside the approved boundary, even briefly, is not covered by the FRIA exception.
4

Confirm the aircraft's registration status separately

A FRIA removes the Remote ID equipment requirement only. If the aircraft is otherwise required to be registered under Part 47 or Part 48, that requirement still applies regardless of the FRIA.

Step Section What it covers
Eligibility14 CFR 89.205Only a recognized community-based organization or an educational institution may apply
Requests for establishment14 CFR 89.210Applicant identity, contact, location, purpose, and existing site agreements
Approval14 CFR 89.215FAA evaluates airspace restrictions, safety impact, ground security, proximity to other FRIAs
Amendment14 CFR 89.220Changes reported within 10 calendar days; boundary changes require FAA approval first
Duration14 CFR 89.225Valid 48 calendar months; renewal requested at least 120 days before expiration
Expiration/termination14 CFR 89.230Automatic expiration, voluntary termination, or FAA-initiated termination with a 30-day reconsideration window
Mistake Why it happens Correct understanding Regulation / source
Assuming any individual remote pilot can apply to establish a FRIAOther Part 107 processes, like waivers, can be requested by an individual pilotOnly a community-based organization recognized by the FAA or an educational institution is eligible under 89.20514 CFR 89.205
Believing flying inside a FRIA exempts the aircraft from registrationBoth Remote ID and registration are tied to the same underlying rule structureA FRIA removes only the Remote ID equipment/broadcast requirement; registration under Part 47 or Part 48 is a separate requirement that still applies14 CFR 89.105, Part 48
Assuming BVLOS is allowed inside a FRIA since no equipment is neededThe lack of equipment feels like it should also relax other operating limitsAircraft and pilot must both remain within the boundary and within VLOS at all times; the FRIA exception does not authorize BVLOS14 CFR Part 89, Subpart C
Assuming a FRIA's approval lasts indefinitely once grantedSome FAA authorizations, like a remote pilot certificate, last for years without a fixed short expirationFRIA approval is valid for only 48 calendar months and must be renewed at least 120 days before it expires14 CFR 89.225

How do I find an FAA-Recognized Identification Area near me?

Check the FAA's official Remote ID resources for current, approved FRIA locations before flying without Remote ID equipment. Never assume a field is an approved FRIA based on reputation alone; approvals are time-limited and must be verified as current.

Does operating inside a FRIA exempt my aircraft from registration?

No. A FRIA removes only the Remote ID equipment and broadcast requirement. If the aircraft is otherwise required to be registered under 14 CFR Part 47 or Part 48, that requirement is unchanged.

Can I fly beyond visual line of sight inside a FRIA since I don't need Remote ID equipment there?

No. Both the aircraft and the pilot must remain within the FRIA's approved boundary, and the operation must stay within visual line of sight throughout the flight.

Test Your Knowledge

Answer the questions below to check your understanding. Every answer can be found in the lesson above.

Loading questions...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.