OMB Control No. 3060-XXXX
June 2025
Supporting Statement
Sections 88.27, 88.31, 88.33, 88.35, 88.135, 88.137, 88.141;
Uncrewed Aircraft Communications in the 5030-5091 MHz band
1. Explain the circumstances that make the collection of information necessary. Identify any legal or administrative requirements that necessitate collection. Attach a copy of the appropriate section of each statute and regulation mandating or authorizing the collection of information.
On August 21, 2024, the Federal Communications Commission (“Commission” or “FCC”) adopted a Report and Order, Spectrum Rules and Policies for the Operation of Unmanned Aircraft Systems, FCC 24-91, in WT Docket No. 22-323 (Report and Order), establishing rules for Uncrewed Aircraft System Services (UASS), to enable uncrewed aircraft systems (UAS) operators to obtain direct frequency assignments in a portion of the 5030-5091 MHz band to support interference-protected communications between UAS operators on the ground and uncrewed aircraft (UA) for flight control and telemetry. Referred to as “non-networked access” (NNA), these direct frequency assignments can support highly reliable control links, and thereby help to safely integrate UAS flights into the National Airspace System (NAS) and promote the development of a diverse range of beneficial public and private uses of UAS technology.
Under the new rules, operators’ use of the spectrum designated for NNA (the 5040-5050 MHz portion of the 5030-5091 MHz band) will be authorized and coordinated by one or more dynamic frequency management systems (DFMSs). UAS operators must register with a Commission-approved DFMS, and then may request short-term frequency assignments in the NNA spectrum from the DFMS. NNA users may transmit in the spectrum only using rule-compliant NNA stations and only pursuant to and consistent with the terms of a frequency assignment from a DFMS.
A DFMS is a frequency coordination system operating in the 5030-5091 MHz band that (1) is highly automated and capable of providing rapid responses to frequency assignment requests from registered NNA operators, and (2) in response to such requests, is capable of assigning to the requesting operator temporary protected use of certain frequencies for a particular geographic area and time period tailored to the operator’s submitted operation, to the extent such frequencies are available. The DFMSs will coordinate the different UAS operators in the band, and will coordinate with each other to ensure that assignments from different DFMSs are consistent.
DFMSs will also be responsible for ensuring that authorized UAS operations do not cause interference to Microwave Landing Service (MLS), to the extent any MLS systems are deployed in the 5030-5091 MHz band. An MLS system is a radio guidance system intended to be installed at airports to aid aircraft in landing in circumstances such as when an airport is visually obscured by bad weather. MLS systems have priority over other operations in the 5030-5091 MHz band. Although there are no non-federal MLS systems in the band, there may be some federal systems deployed at certain military facilities. DFMSs are required to retain information on, and enforce, exclusion zones sufficient to protect any federal MLS stations in the 5030-5091 MHz band. The DFMSs will also be responsible for implementing a process for coordination with the Administrator of the National Radio Quiet Zone (NRQZ) to the extent an NNA user seeks a frequency assignment with the NRQZ, in order to protect radio astronomy occurring in that area.
A DFMS must perform several other functions, including, among others:
Provide a process for NNA users to register with the system for the purpose of enabling such users to submit frequency assignment requests and obtain frequency assignments.
Be capable of processing frequency assignment requests nationwide and across the entire 5030-5091 MHz band.
Be capable of responding to in-flight revision requests.
Be capable of communicating directly with a UAS ground station operating in the NNA spectrum, or with proxy software acting on the ground station’s behalf, to achieve the following: (1) ensure that all NNA stations used in an operation, including any ground or airborne station used in the flight, are programmed to limit communications in the 5030-5091 MHz band, during the period of the frequency assignment, to the specific frequencies assigned by the DFMS and in accordance with the other terms of the assignment; and (2) receive updates on flight status.
Communicate and coordinate with other DFMSs as necessary to ensure consistent data and assignments, the safe and robust operation of authorized services, and compliance with the rules when a UA has launched and when it has landed.
Verify that the NNA stations to be used in operations are FCC-certified devices and must not provide assignments to an uncertified device.
Maintain all records for at least 60 months, including but not limited to date, time, and requester identification records for all requests for, approval of, denial of, or termination of approval for all assignments of frequencies or revisions of such assignments, and all certifications submitted in connection with such requests.
The Commission is requesting that the Office of Management and Budget (OMB) approval for an information collection consisting of the following requirements that were adopted to enable the implementation of the rules for NNA operations, including the establishment and operation of the automated process of frequency assignments through DFMSs:
Registration and Request Requirements (47 C.F.R. §§ 88.27(c); 88.31(a), (c), (d), (e); 88.33; 88.35; 88.135(a), (b), (h), (j))
All NNA users are required to register once with a DFMS in order to submit requests to that DFMS for a short term assignment of frequencies that authorize the user to transmit in the NNA spectrum. Registrations must include a party’s legal name and contact information, and any other information required by the DFMS, and all DFMSs must require the same registration and frequency assignment request information. (47 C.F.R. § 88.27(c); 88.33(a); 88.135(a), (b)). Following registration, the NNA user may submit a request to the DFMS for a temporary frequency assignment to support UAS control communications, limited to the duration and geographic coverage necessary to support a single submitted UAS flight. (47 C.F.R. § 88.31(a)). For each frequency assignment request, the NNA user will be required to certify that it has flight authorization from the Federal Aviation Administration (FAA) to cover the flight associated with the frequency assignment request, and that any remote pilots that will be involved in the flight have all necessary FAA remote pilot authorization, to the extent such authorization is required. (47 C.F.R. § 88.135(h)). When either registering with or making a request to a DFMS, the NNA user must comply with all DFMS Administrator instructions, including those regarding registration process and procedures, requests and other submissions to the DFMS, and operational use of NNA assignments. (47 C.F.R. § 88.31(c)). Information submitted to a DFMS with registration or assignment requests must be accurate, complete, and made in good faith. (47 C.F.R. § 88.33(a)). Further, parties must keep registration information up to date, and must keep frequency assignment request information up to date until the scheduled time of the operation. (47 C.F.R. § 88.33(b)). These registration and request requirements are necessary to effectively and efficiently implement a system that will enable a DFMS to make automated, short term frequency assignments for UAS control communications on a safe, efficient, and coordinated basis.
Any UAS ground station using an NNA assignment to support a UAS flight, or proxy software acting on the ground station’s behalf, must be capable of communicating with the assigning DFMS to achieve the following: (1) confirm that all NNA stations used in the operation, including any UAS ground station or airborne station used in the flight, are programmed to limit communications in the 5030-5091 MHz band, during the period of the frequency assignment, to the specific frequencies assigned by the DFMS and in accordance with the other terms of the assignment, and (2) send updates on flight status when an uncrewed aircraft has launched and when it has landed. Similarly, a DFMS must be capable of communicating with a UAS ground station operating in the NNA spectrum or with proxy software acting on the ground station’s behalf to achieve these purposes. (47 C.F.R. § 88.31(e); 88.135(j)). These requirements are necessary to reduce the probability of UAS control communications occurring outside of authorized parameters, which would increase the probability of harmful interference occurring and undermine the reliability of the UAS control communications in this band.
In the event that NNA users seek assignments with the NRQZ, they are required to first notify the NRQZ Administrator in writing of the technical details of the proposed operation. (47 C.F.R. § 88.31(d); 88.35(a)). The notification must include the geographical coordinates of ground station antenna locations, associated ground station antenna height, antenna directivity (if any), the maximum airborne station altitude, the maximum airborne station flight altitude (MSL or AGL), the frequencies, the emission type, and power. (47 C.F.R. § 88.35(a)). If an operation or revision of an operation is within the scope, including any applicable conditions, of a previously granted approval from the NRQZ Administrator, parties need not provide notification of the operation or revision to the NRQZ Administrator, but must submit the approval with any frequency assignment request relying on this exception. (47 C.F.R. § 88.35(b)(1)). If the NRQZ Administrator establishes criteria for NNA operations in the NRQZ that do not require notification to the NRQZ Administrator, and an operation or revision of an operation is within the scope of such criteria, a party need not provide notification of the operation or revision to the NRQZ Administrator, but, when submitting their request, must certify that their request meets the criteria for NNA operations in the NRQZ that do not require notification to the NRQZ Administrator and provide any additional supporting documentation required by the DFMS. (47 C.F.R. § 88.35(b)(2)). When a request subject to notification requirements is made to a DFMS, the request must state the date that notification was made. The notification can be made prior to or simultaneously with the request; if the notice is made prior to the request, the requesting party must also provide notice to the NRQZ Administrator upon actual submission of the request with the DFMS, specifying which DFMS has received the request. (47 C.F.R. § 88.35(c)). These requirements are necessary to ensure that radio astronomy observations within the NRQZ are adequately protected from harmful interference from UAS communications in the band.
Dynamic Frequency Management System (DFMS) Requirements, Administrator Requirements, and Authorization (47 C.F.R. §§ 88.135(p), (q), (x); 88.137(d))
Protection of MLS. A DFMS must retain information on exclusion zones sufficient to protect MLS in the 5030-5091 MHz band, which is necessary to enable the DFMS to enforce these exclusion zones in its frequency assignments. (47 C.F.R. § 88.135(p)).
General requirement for retention of records. A DFMS must maintain all records for at least 60 months, including but not limited to date, time, and requester identification records for all requests for, approval of, denial of, or termination of approval for all assignments of frequencies or revisions of such assignments, and all certifications submitted in connection with such requests. (47 C.F.R. § 88.135(q)). This is necessary both to ensure that the Commission can perform adequate oversight and to facilitate transfer of responsibilities to a new DFMS in the event of the termination of a DFMS’s operations.
Notification of NSF. A DFMS must immediately notify the National Science Foundation (NSF), Division of Astronomical Sciences, Electromagnetic Spectrum Management Unit, when a request for frequency assignment is approved that will support operation of a UAS within 25 miles of one of sixteen specified radio astronomy sites. Notification must include the operation details. (47 C.F.R. § 88.135(x)). This notification will help to facilitate co-existence of UAS systems and radio astronomy systems.
Transfer of information. A DFMS Administrator is required to securely transfer all the information in the DFMS to another approved entity in the event it does not continue as the DFMS administrator at the end of its term. It may charge a reasonable price for such conveyance. (47 C.F.R. § 88.137(d)). This requirement is necessary to ensure that operations in and coordination of the band are not disrupted if one or more DFMS ceases operations.
Prospective DFMS Administrators must apply to, and be approved by, the Commission prior to commencing operation of a DFMS. This requirement is necessary to ensure that DFMS Administrators are qualified to perform the required functions.
Interim Access Mechanism (47 C.F.R. §§ 88.35(b); 88.141(b))
Prior to approval and commencement of operation by the first DFMS administrator, NNA users may access the 5040-5060 MHz band for protected NNA communications through the Interim Access Mechanism (IAM). Under this mechanism, NNA users seeking to transmit in the band must first request and obtain concurrence from the FAA for the requested use, and upon receipt of FAA concurrence, must submit to the FCC an online registration form certifying that (1) they have complied with the FAA concurrence process; (2) the operation is in compliance with the Commission’s NNA rules and technical requirements; (3) all equipment utilized in the operation meets equipment certification requirements; and (4) the frequency assignment terminates immediately in the event a DFMS becomes operational. Upon submission of this registration form, they may use the band for operations within the scope of the rules subject to any conditions in the FAA concurrence. (47 C.F.R. § 88.141(b)). These requirements are necessary to achieve the necessary coordination and to ensure that operations are compliant with the rules in the absence of a DFMS.
When a request for concurrence is submitted to the FAA under the IAM for operations within the NRQZ, the request must state the date that notification to the NRQZ Administrator was made or provide an approval from the NRQZ Administrator for operations within the NRQZ or portions thereof along with the maximum operating altitude allowed. (47 C.F.R. § 88.35(b)). This requirement is necessary to provide protection of radio astronomy in the NRQZ during the IAM period before a DFMS is operational. All access to the band pursuant to the IAM will cease once the first DFMS administrator begins operation. After that time, operators may not submit any additional requests under the IAM or continue to operate under prior IAM-approved requests, may only access 5040-5050 MHz (rather than the 5040-5060 MHz permitted under the IAM), and only pursuant to DFMS assignment.
Statutory Authority: The Commission adopted the requirements pursuant to its authority in Sections 1, 4, 301, 303, 307, and 310 of the Communications Act of 1934, as amended, 47 U.S.C. §§ 151, 154, 301, 303, 307, and 310.
This information collection does not affect individuals or households – respondents are limited to applicants, protected entities and licensees using the subject radio frequency (RF) spectrum. Thus, there is no impact under the Privacy Act and a Privacy Impact Assessment is not required.
2. Indicate how, by whom and for what purpose the information is to be used. Except for a new collection, indicate the actual use the agency has made of the information received from the current collection.
Registration and request information will be submitted to a DFMS by a party seeking a temporary frequency assignment in the NNA spectrum for UAS control communications. This information will be for to a DFMS in order to facilitate the short term assignment of frequencies in the 5030-5091 MHz band to particular UAS operators for the purpose of UAS control communications.
A DFMS will use the communications from the UAS ground station to confirm that UAS communications in the band are consistent with its assignments, and to confirm when assigned frequencies are no longer in use and thus available for reassignment.
Notifications sent to the Director of the NRQZ are used by the Director to determine whether to file objections to a requested assignment with the relevant DFMS, which helps to protect radio astronomy observations in the NRQZ.
MLS exclusion zone information will be used by the DFMS in determining those areas where precluding NNA users from frequency assignments is necessary to protect MLS. DFMS general record retention requirements will support FCC oversight and ensure that, in the event a DFMS ceases operations, operations can be transferred to another DFMS without disruption.
The NSF will use notification of the details of operations associated with frequency assignments within 25 miles of one of sixteen specified radio astronomy sites to avoid interference by coordinating observations with the operations or taking other measures to facilitate co-existence.
DFMS information transferred to another DFMS will be used by the receiving DFMS to continue the coordination functions in the band without disruption.
The Commission will collect information from DFMS applicants to determine whether they meet the qualifications to manage the database and coordinate UAS frequency assignments.
The Commission will collect registration information from parties seeking frequencies under the Interim Access Mechanism to keep track of who is using the spectrum during this period and ensure that parties using the spectrum have complied with the requirements for spectrum use during the period before a DFMS is operational.
3. Describe whether, and to what extent, the collection of information involves the use of automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, e.g., permitting electronic submission of responses, and the basis for the decision of adopting this means of collection. Also describe any consideration of using information technology to reduce the burden.
The Commission believes information technology will reduce the burden on the public, as the DFMS will collect registration and request information via electronic means.
4. Describe efforts to identify duplication. Show specifically why any similar information already available cannot be used or modified for use for the purposes described in Item 2 above.
The UASS, NNA rules, and the DFMSs were established by the Report & Order and all associated information collection requirements are new. Therefore, there is no similar data available and there is no duplication of effort by the FCC or any other agency.
5. If the collection of information impacts small businesses or other small entities, describe any methods used to minimize the burden.
As the reporting, recordkeeping, and other compliance requirements resulting from the Report and Order are necessary to enable the successful sharing of spectrum in the band, they will apply to all entities in the same manner. The Commission does not believe that the costs and/or administrative burdens associated with the rules will unduly burden small entities. The Commission will work with the DFMS Administrators to ensure that information is collected in the least burdensome manner to all businesses, both large and small.
6. Describe the consequence to Federal program or policy activities if the collection is not conducted or is conducted less frequently, as well as any technical or legal obstacles to
reducing burden.
If NNA users did not provide registration and request information, a DFMS would not able to accurately assign channels and frequencies and provide approval for UAS control communications in the band. Request-specific information cannot be gathered less frequently than on a per-request basis. Other reporting requirements in connection with DFMS operations, including NSF and NRQZ notification and DFMS records transfer, are likewise imposed in the circumstances that require the information. If this information less frequently, a DFMS would not be able to properly fulfill its role to authorize and coordinate communications and ensure protection of authorized services. Similarly, the IAM could not be implemented absent reporting requirements for IAM requests on a per-request basis.
7. Explain any special circumstances that would cause an information collection to be conducted in a manner inconsistent with the general information collection guidelines in 5 CFR 1320.5 (e.g. payment to respondents, disclosure of proprietary information, etc.):
NNA users will be required to submit request information each time they submit a new request to a DFMS, which may happen more often than quarterly. Duration of the requested frequency assignments must be limited to support a single flight and last no more than one day. Therefore, if an NNA user needs assignments on multiple days during a quarter, it will be required to provide information to the DFMS more often than quarterly. However, processing of requests necessarily requires submission of the information supporting the request. Further, limiting assignments to a single UAS flight lasting no more than 24 hours will help to promote efficient usage of the limited amount of spectrum available for NNA, ensuring that NNA users will have exclusive use of frequencies for flight control only during the flight, after which the frequencies will be available for use by another NNA user.
8. (a) If applicable, provide a copy and identify the date and page number of publication in the Federal Register of the agency's notice, required by 5 CFR 1320.8(d), soliciting comments on the information collection prior to submission to OMB. Summarize public comments received in response to that notice and describe actions taken by the agency in response to these comments. Specifically address comments received on cost and hour burden.
(b) Describe efforts to consult with persons outside the agency to obtain their views on the availability of data, frequency of collection, the clarity of instructions and recordkeeping, disclosure, or reporting format (if any), and on the data elements to be recorded, disclosed, or reported.
(c) Consultation with representatives of those from whom information is to be obtained, or those who must compile records, should occur at least once every three years -- even if the collection of information activity is the same as in prior periods. There may be circumstances that mitigate against consultation in a specific situation. These circumstances should be explained.
The Commission published a notice in the Federal Register (90 FR 15003) on April 7, 2025, seeking comments from the public on information collection requirements contained in this collection. No comments were received from the public that specifically addressed the information collections.
9. Explain any decision to provide any payment or gift to respondents, other than remuneration of contractors or grantees.
No payment or gift was provided to the respondents that is associated with this collection of information.
10. Describe any assurance of confidentiality provided to respondents and the basis for the assurance in statute, regulation, or agency policy.
The Commission is not requesting respondents to submit confidential information.
11. Provide additional justification for any questions of a sensitive nature, such as sexual behavior and attitudes, religious beliefs, and other matters that are commonly considered private. This justification should include the reasons why the agency considers the questions necessary, the specific uses to be made of the information, the explanation to be given to persons from whom the information is requested, and any steps to be taken to obtain their consent.
This information collection does not raise any questions or issues of a sensitive nature.
12. Provide estimates of the hour burden of the collection of information. The statement should indicate the number of respondents, frequency of response, annual hour burden, and an explanation of how the burden was estimated. If the hour burden on respondents is expected to vary widely because of differences in activity, size, or complexity, show the range of estimated hour burden, and explain the reasons for the variance.
Provide estimates of annualized costs to respondents for the hour burdens for collection of information, identifying and using appropriate wage rate categories. The cost of contracting out or paying out-side parties for information collection activities should not be included here. Instead, this cost should be included in Item 13.
Registration (47 C.F.R. §§ 88.27(c); 88.33(a); 88.135(a),(b)). It is estimated that approximately 200 NNA users will register with a DFMS per year, and that registration will require half an hour. The registration will be submitted electronically and need only be submitted once per NNA user.
200 NNA users x 1 x .5 hrs./registration = 100 hours
Frequency assignment requests (47 C.F.R. §§ 88.31(a), (c); 88.33(a); 88.135(h)). Because frequency assignments will be tailored to a single flight, and further limited to no longer than 24 hours, NNA users will likely need to file multiple requests to cover different flights as they occur throughout the year. It is estimated that a typical NNA user will file 40 requests per year, and that filing requests will require half an hour. The requests will be submitted electronically. In rare cases, NNA users that receive an assignment may need to request a revision of the assignment (for example, because of a need to change the duration or path of a flight). It is anticipated that this will occur for 10% of the requests.
Requests: 200 NNA users x 40 requests/year x .5 hrs./request = 4,000 hours
Request Revision: 80 requests/year x .5 hrs./request = 40 hours
Ground station-to-DFMS communications (47 C.F.R. §§ 88.31(e); 88.135(j)): The required communications will occur once for each of 8000 assignments, per above (200 NNA users x 40 assignment requests/user), anticipated frequency is 8000/year. However, it is anticipate that station-to-DFMS communications will occur automatically, and therefore impose a negligible burden on operators.
Station-to-DFMS Communications: 200 NNA users x 40 assignments/year x 0 hrs/communication = 0 hours
NRQZ submission (47 C.F.R. §§ 88.31(d); 88.35(a)-(c)): It is estimated that, of the 8000 frequency assignment requests, 10 will be for assignments in the NRQZ, and that 5 of these will require filing notification to the Director of the NRQZ. It is anticipated that filing the notification will take .5 hours.
NRQZ submission: 5 submissions x .5 hours = 2.5 hours
Retention of MLS information (47 C.F.R. § 88.135(p)): It is estimated that there will be five DFMSs in the band. Initial obtaining MLS information from the Commission is estimated to require .5 hours. Retention of MLS information will involve no additional processing time.
Retention of MLS information: 5 DFMSs x .5 hours = 2.5 hours
Notification of NSF (47 C.F.R. § 135(x)): It is estimated that, of the 8000 frequency assignments, 50 assignments (10 assignments each from 5 DFMSs) will be assignments that will support operation of a UAS within 25 miles of one of sixteen specified radio astronomy sites. It is anticipated that this notification will occur by automated process and will impose no burdens.
Notification of NSF: 50 assignments x 0 hours = 0 hours
DFMS records transfer (47 C.F.R. § 88.137(d)): It is not anticipated that any DFMS will cease operations during this collections period. However, if one does so, it is estimated that the process of records transfer will be electronic and require 1 hour.
DFMS records transfer: 1 transfer x 1 hour/transfer = 1 hour
DFMS administrator application: It is estimated that five entities will apply to be administrators of a DFMS, and that each application will require 10 hours to prepare.
DFMS administrator application: 5 applications x 10 hours/application = 50 hours
Interim access mechanism (47 C.F.R. § 88.141(b): It is estimated that there will be 2 requests per year from 15 parties (30 requests per year) for access under the IAM. The lower rate of access requests under the IAM is anticipated because (1) requests under the Interim Access Mechanism are not restricted to assignments for single flights, and accordingly, during this IAM period, parties can make single requests covering an extended period covering many flights rather filing a separate assignment request for each flight; and (2) because the IAM will apply during the first years after the rules are effective, there is anticipated to be less available equipment for the band, and therefore fewer entities seeking to use it. It is estimated that filing a request for concurrence with the FAA will require .5 hours, and that registering with the FCC will require .25 hours.
Interim access mechanism: 30 requests x .75 hours/request = 22.5 hours
Burden to the Respondents:
Registration = 100 hours
Requests and Request Revisions = 4,040 hours
Station-to-DFMS Communications = 0 hours
NRQZ Submission = 2.5 hours
Retention of MLS Information = 2.5 hours
Notification of NSF = 0 hours
DFMS Records Transfer = 1 hour
DFMS administrator application = 50 hours
Interim access mechanism = 22.5 hours
Total Burden: 4,218.5 hours rounded to 4,219
Total Number of Respondents is: 436 respondents
Total Number of Annual Responses: 8,326 responses
Total Hour Burden is: 4,218.5 hours (rounded to 4,219 hours)
The Commission estimates the following in-house costs to respondents for each collection based on its knowledge of its respondents providing this information:
Registration: 200 (NNA users) x 1 response x .5 hrs. x $65.48/hr. (based on salary for 2025 GS-13, Step 5, general schedule, federal government employee) = $6,548
Frequency assignment requests: 200 (NNA users) x 40 requests x .5 hrs. x $65.48/hr. = $261,920
Frequency assignment request revision: 80 requests/year x .5 hrs. x $65.48/hr. = $2,619.20
Ground station-to-DFMS communications: 200 (NNA users) x 40 assignments/yr. x 0 hrs x $65.48/hr. = $0
NRQZ submission: 5 (NNA users) x .5 hrs. x $65.48/hr. = $163.70
Retention of MLS information: 5 (DFMSs) x .5 hrs. x $65.48/hr. = $163.70
Notification of NSF: 50 requests x 0 hrs. x $48.07/hr. = $0
DFMS records transfer: 1 x 1hr. x $65.48/hr. = $65.48
DFMS administrator application: 5 applications x 10 hrs. x $65.48/hr. = $3,274
Interim access mechanism: 30 requests x .75 hrs/request x $65.48/hr. = $1,473.30
Total In-House Cost to Respondents = $276,227.38
13. Provide an estimate of the total annual cost burden to respondents or
record keepers resulting from the collection of information. Do not include the cost of any burden hours shown in items 12 and 14.
The Commission estimates the following costs to respondents based on its knowledge of similar past applications for automated coordination systems in other bands:
DFMS Administrator Authorization: 5 (applicants) x 2 hrs. x $300/hr. (outside legal counsel) = $3,000
14. Provide estimates of annualized costs to the Federal government.
Registration: NNA users will provide this information directly to a DFMS and there is no cost to the federal government.
$0
Frequency assignment requests: NNA users will provide this information directly to a DFMS and there is no cost to the federal government.
$0
Ground station-to-DFMS communications: Ground stations will provide this information directly to a DFMS and there is no cost to the federal government.
$0
NRQZ submission: NNA users will provide this information directly to the NRQZ Director and there is no cost to the federal government.
$0
Retention of MLS information:
$0
Notification of NSF (47 C.F.R. § 135(x)): A DFMS will provide this notification directly to the NSF, and there is no cost to the federal government.
$0
DFMS records transfer (47 C.F.R. § 88.137(d)): Transfer of records will be between two private entities and there is no cost to the federal government.
$0
DFMS administrator application: It is estimated that it will take an engineer and an attorney, both earning at 65.48hr based on the salary for 2025 GS-13, Step 5, Washington-Baltimore-Arlington schedule, sixteen hours each to review each of five applications for authorization.
5 (applicants) x 2 federal staff x 16 hrs. x $65.48/hr. = $10,476.80
Interim access mechanism: It is estimated that it will take a staff person earning $65.48/hr., based on the salary for 2025GS-13, Step 5, Washington-Baltimore-Arlington schedule, four hours to set up the registration webpage. It is not anticipated that registrations will be routinely reviewed.
1 x 4 hours x $65.48/hr = $261.92
Total cost to the Federal Government is: $10,738.72
15. Explain reasons for any program changes or adjustments reported in Items 12 and 13.
These are all new information collections. Therefore, the information collections adopted in FCC 24-91 will add 436 respondents, 8,326 annual responses, 4,219 annual burden hours and $3,000 in annual cost to OMB’s inventory once the collection is approved.
16. For collection of information whose results are planned to be published for statistical use, outline plans for tabulation, statistical analysis, and publication. Address any complex analytical techniques that will be used. Provide the time schedule for the entire project, including beginning and ending dates of the collection of information, completion of report, publication dates, and other actions.
The Commission does not intend to publish the results of these collections of information.
17. If seeking approval to not display the expiration date for OMB approval of the information collection, explain the reasons that display would be inappropriate.
The Commission is not seeking approval not to display the expiration date for OMB approval of these collections of information.
18. Explain each exception to the certification statement.
There are no exceptions to the certification statement.
B. Collections of Information Employing Statistical Methods.
This collection of information does not employ statistical methods.
| File Type | application/vnd.openxmlformats-officedocument.wordprocessingml.document |
| Author | Peter Trachtenberg |
| File Modified | 0000-00-00 |
| File Created | 2025-06-18 |