5010 Airport Inspections
What is a 5010 Inspection?
The 5010 program is named for the Federal Aviation Administration (FAA) Order that created the Airport Safety Data Program: FAA Order 5010. The Airport Safety Data Program, now called Airport Data and Information Management, is the primary means for the collection, maintenance, and dissemination of information about airports. Airport information is housed in the Airport Master Records and maintained by the FAA.
MnDOT has been delegated authority to collect and forward information on Minnesota Airports to the FAA for use in publications such as the Airport/Facility Directory and instrument approach procedures. MnDOT also publishes the collected information in the Minnesota Airport Directory and Travel Guide. These two publications provide pilots with necessary information for planning their flights.
While collecting information, MnDOT also conducts an onsite airport inspection (5010 Inspection) to verify that the airport meets the standards of Federal Aviation Regulations (FAR) Part 77 and the Minnesota airport licensing standards. These standards set minimum safety requirements to be maintained by each airport.
After the 5010 Inspection, MnDOT processes the collected data and sends out a results packet with a letter that explains the findings. The results packet lists any deficiencies identified during the inspection. The results packet is also forwarded to the FAA. If the FAA finds it necessary, they may restrict approaches or place limitations upon the airport due to certain findings.
It is the airport's responsibility to address each deficiency. Once the airport has a plan to correct them, MnDOT should be notified as soon as possible, but no later than 60 days. Another follow-up letter should be sent to MnDOT and the FAA once the deficiencies have been corrected to prevent any restrictions from being placed on the airport.
5010 Inspection Schedule
MnDOT Office of Aeronautics inspects all Minnesota public-use airports on a recurring three year basis. At the beginning of each year, MnDOT staff will be contacting airport managers to determine a convenient date and time to arrange an inspection.
Preparing for a 5010 Inspection
Prior to a 5010 Inspection, airport managers should review the results of the previous inspection. The previous inspection letter will detail any discrepancies noted. An aerial image will be included with the letter that depicts obstructions that penetrate the FAR Part 77 surfaces. Trees, brush and crops are typical obstructions seen during an inspection and can be avoided by trimming at the locations noted on the aerial image. A copy of the airport's previous inspection results can be requested from MnDOT Office of Aeronautics.
MnDOT agricultural guidelines (PDF) go over boundaries to be maintained around the airport. These guidelines should be reviewed with local farmers prior to each planting season.
Airport based aircraft records should be updated by the airport manager, or designee, at airports that are in the National Plan of Integrated Airport Systems (NPIAS) and are eligible for Federal funding under the Airport Improvement Program (AIP). Federal funding can ultimately be determined by these reports. To sustain eligibility for Federal funds, based aircraft records should be maintained on a yearly basis.
Airports can review an annual calendar (PDF) of suggested ongoing/recurring tasks which can be done to maintain the airport in between 5010 Inspections.
Current 5010/Airport Master Record Data
The Airport IQ web site houses the most current FAA Airport Master Records and Reports. If any information in these records is incorrect, MnDOT provides guidance on how to contact the National Flight Data Center (PDF) to make changes.
All 5010 inspection letter requests, questions, or comments should be directed to:
Airport Program Administrator