PLSS and Oil & Gas Well Permitting: APD Workflow Guide for 2026

The Application for Permit to Drill requires two things that are easy to mix up: the PLSS legal description from the lease, and geographic coordinates that actually match it. Getting one right while the other has a transposed digit is the most common reason a permit package comes back for correction before a reviewer has even looked at the substance.

This guide covers what APD filings specifically require for APD PLSS coordinates in 2026, how the three major permitting systems handle them, where errors consistently show up, and how to process a multi-well package without spending a week on manual lookups.

What PLSS Data an APD Filing Requires

BLM Form 3160-3 — the federal APD — requires the well location in three forms:

• Legal description: Township, Range, Section, and aliquot part down to the quarter section or smaller. Example: T44N R72W Sec 15 NE¼, 6th Principal Meridian.
• Latitude/longitude: Decimal degrees, WGS84 datum, six decimal places minimum.
• Footage from section lines: Distance from the proposed wellhead to the nearest north/south and east/west section lines, in feet.

All three must be internally consistent. If the coordinates you submit don't fall within the described section, the application comes back. BLM's automated systems cross-check the legal description against the submitted coordinates — the days of a reviewer manually eyeballing it are largely over.

State permits require the same core data, though form fields and validation rigor vary by system.

State-by-State Permitting Systems: WellSTAR, OCC, and RRC

Most federal APDs in the Rocky Mountain region go through WellSTAR, BLM's electronic filing system. WellSTAR validates PLSS descriptions at submission — it checks that the Township, Range, and Section combination exists in the CadNSDI database and that the entered coordinates fall within the section polygon. An out-of-range coordinate triggers an immediate validation error before the application reaches a reviewer.

Oklahoma's OCC (Oklahoma Corporation Commission) handles state well permitting for the STACK, Anadarko, and Arkoma basins. Oklahoma uses two PLSS meridians: the Indian Meridian covers most of the state, while the Cimarron Meridian governs the Panhandle. The OCC's OAP system is less automated than WellSTAR on coordinate cross-checks, but reviewers flag inconsistencies — especially when footage from section lines doesn't match the submitted latitude/longitude. A filing for T14N R9W Sec 22 under the wrong meridian puts your well location roughly 200 miles from where the lease actually is.

Texas's RRC (Railroad Commission) is a special case. Most of Texas uses the Texas General Land Office survey system — Abstract and Survey blocks, not Township-Range-Section. The Permian Basin's eastern edge and parts of the Panhandle do fall within the PLSS. If you're filing an RRC permit and the lease shows a PLSS description, you're in one of those areas or dealing with a federal mineral interest beneath a Texas surface estate. For the rest of the Permian, PLSS doesn't apply and APD coordinates go straight to lat/long.

For operators with multi-state drilling programs, knowing which permitting system applies matters before you build your data package. WellSTAR will catch coordinate mismatches electronically; OCC may not until a reviewer picks up the file.

Common PLSS Errors That Delay APD Approval

Four errors account for most APD rejections tied to location data:

Transposed range direction. T44N R72W and T44N R72E are hundreds of miles apart. This happens when a landman copies from a lease abstract and flips the compass direction. In the Powder River Basin, R72E doesn't exist near active drilling — but WellSTAR won't reject it on that basis alone if the entered coordinates also drift east.

Wrong meridian. Oklahoma's Indian and Cimarron meridians cover different ground. The same Township-Range-Section notation under each meridian points to entirely different locations. The meridian field is required on federal and state permits alike, and it must match the lease.

Off-by-one section. When aliquot parts sit near a section line, the parent section number sometimes carries over wrong from an earlier filing or an old database record. The NE¼ of Section 7 is adjacent to Section 8 — if the lease description reads "Sec 7 NE¼" but the parcel is actually in Section 8, your footage calculations will be off by the full section width.

Stale survey descriptions. Older leases sometimes reference GLO descriptions that predate resurveys. A patent description of "T155N R95W Sec 8 NW¼, 5th Principal Meridian" in the Williston Basin may not align with current CadNSDI boundaries if the section was resurveyed. For leases tracing back to original GLO patents, the BLM GLO Records field guide covers how to reconcile historical patent descriptions with current survey data.

The fastest way to catch any of these before submission: convert every PLSS description in your APD package to coordinates and plot the results. If a point lands in a river, a different county, or a neighboring state, you have a data problem. The PLSS converter handles individual lookups in seconds.

Batch Conversion for Multi-Well APD Packages

A 20-well package with each location requiring coordinate verification is a full afternoon of manual work. The batch conversion tool accepts a CSV of PLSS descriptions and returns coordinates for all of them at once, with any unresolvable entries flagged for review.

The workflow:

1. Export PLSS descriptions from your land management system into a CSV.
2. Upload to the batch converter. Add the principal meridian as a column if your system doesn't include it in the description string.
3. Review flagged entries — the tool marks descriptions it can't resolve.
4. Export the results with coordinates appended.
5. Cross-check against your footage calculations before entering values into WellSTAR or OCC.

For operators running Bakken programs across North Dakota, the volume of descriptions per drilling program can be substantial. Batch processing handles that scale without per-conversion fees that accumulate quickly on large packages. The oil and gas industry page has more on how land departments have structured these workflows.

API Integration for Automated PLSS Lookup

If your land department manages well records in an internal database, automating the coordinate lookup step removes a manual touchpoint entirely. The Township America API accepts a PLSS legal description and returns GeoJSON with the centroid coordinates, section polygon, state, county, and principal meridian — everything needed to populate the location fields on a permit form.

For teams already running Python, pip install townshipamerica wraps the API with typed models and handles batch requests natively. For a detailed walkthrough of integrating APD PLSS coordinates into a land management system, the PLSS API for APD workflows post covers the full integration pattern with code examples for single and batch lookups.

APD Workflow Checklist: From Lease Description to Filed Permit

Before submitting any APD package — federal or state — run through these steps:

• Identify the correct principal meridian for every legal description. Check the lease itself, not the geologist's prospect report.
• Convert all PLSS descriptions to coordinates using current CadNSDI data, not an older GIS shapefile.
• Plot each location on a map and confirm it falls in the expected basin and county.
• Calculate footage from section lines and verify it's consistent with the aliquot part described.
• Cross-check any parcels near section boundaries against adjacent sections.
• Confirm state vs. federal jurisdiction — federal mineral interests file through BLM even on private surface.
• For Oklahoma filings, verify Indian Meridian vs. Cimarron Meridian before entering any Township-Range-Section data.
• For leases pre-dating 1960, review the description against current survey data rather than assuming it maps cleanly.

For operators filing APD PLSS coordinates across multiple basins in 2026, electronic permitting systems now cross-check your location data automatically. A transposed range number means a resubmission, not a phone call. Running the descriptions before they reach the form is the step that catches problems while they're still cheap to fix.

Try the PLSS converter on your next APD package, or see batch and API options if your land department handles more than a few permits per week.