WELL · 42-395-30670 · DISTRICT 5

Autrey Unit #1

Plugged

Robertson County · Bald Prairie (CV Consolidated) field  · Vertical

Autrey Unit #1 (API 42-395-30670) is a plugged well in Robertson County, plugged December 31, 2013, last operated by Fortson Oil Company.

The RRC has issued one drilling permit, issued June 12, 2001, permitted to 12,200 ft.

It was permitted by Matador Operating Company and has since transferred to Fortson Oil Company on the wellbore schedule.

Completion filings report 6 formation tops, including Austin Chalk, Paluxy, Rodessa, James Lime.

Operator of record

Fortson Oil Company

Permitted by Matador Operating Company; the EWA schedule now lists a different operator.

Fort Worth, TX · P-5 Y, filed Jun 5, 2020 · 220 permits on file · (682) 351-9015

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleFortson Oil Company
Production reportsFortson Oil Companythrough Jan 2011
Latest permitMatador Operating CompanyJun 12, 2001

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

12,200
total depth, ft
1
permits on file
Jun 12, 2001
last permit issued
Sep 11, 2001
completed
0
cumulative oil, bbl
897K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2001 THROUGH Dec 2014

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 11, 2001
Shut in
—
Plugged
Dec 31, 2013

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Autrey Unit G-5-185368Bald Prairie (CV Consolidated)Fortson Oil Company10897KSep 2001 – Dec 2014

No volumes reported on these leases in the last three years.

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Matador Operating CompanySep 2001 → Jul 2003
  2. 2Brown, Tom Inc.Aug 2003 → Dec 2004
  3. 3Encana Oil & Gas(usa) Inc.Jan 2005 → Oct 2009
  4. 4Fortson Oil CompanyNov 2009 → Jan 2011

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
510163-99DrillMatador Operating CompanyJun 12, 2001Jun 12, 2001Jul 31, 200112,200

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-5-185368————

Formation tops

As filed on W-2/G-1. Subsea from 448 ft elevation.Download CSV →

FormationMD ftSubsea
Austin Chalk4,505-4,057
Paluxy5,912-5,464
Rodessa7,240-6,792
James LimeJAMES7,675-7,227
Cotton Valley10,350-9,902
BossierBOSSIER SHALE10,975-10,527

Perforations

Perforated and open-hole intervals.

FromToType
11,47511,490Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6252,02012.25905 S
5.511,6527.875910 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Nov 28, 2001Oct 15, 2001Yes
00Nov 12, 2001——

The source documents

Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.

About this data

Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.

New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease

Developers: this page as JSON is GET /v1/data/wells/39530670, documented in the API reference.