WELL · 42-165-37427 · DISTRICT 8

Reimer #1

Plugged

Gaines County · Robertson N. (Clear Fork 7100) field  · Vertical

Reimer #1 (API 42-165-37427) is a plugged well in Gaines County, plugged August 27, 2013, last operated by Probity Operating LLC.

The RRC has issued 2 drilling permits (amended twice) between 2011 and 2012, permitted to 9,000 ft.

Completion filings report 2 formation tops, including San Andres, Clear Fork.

Operator of record

Probity Operating LLC

Midland, TX · P-5 Y, filed May 8, 2015 · 32 permits on file · (888) 547-4573

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleProbity Operating LLC
Production reportsnone
Latest permitProbity Operating, LLCDec 20, 2012
9,000
total depth, ft
4
permits on file
Dec 20, 2012
last permit issued
May 22, 2012
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2012 THROUGH Feb 2014

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
May 22, 2012
Shut in
—
Plugged
Aug 27, 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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Reimer O-11-70056Garrett (San Andres)Probity Operating, LLC100Jan 2013 – Feb 2014
Reimer O-11-69996Robertson, N. (Clear Fork 7100)Probity Operating, LLC100May 2012 – Oct 2013

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

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
753094-99RecompletionProbity Operating, LLCDec 12, 2012Dec 20, 2012Jan 15, 20138,516
717811-97DrillProbity Operating, LLCMay 31, 2013Jun 23, 2011Feb 4, 20129,000
717811-98DrillDyad Petroleum CompanyDec 13, 2011Jun 23, 2011Feb 4, 20129,000
717811-99DrillDyad Petroleum CompanyJun 6, 2011Jun 23, 2011—9,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-11-69996————
—— O-11-70056————

Formation tops

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

FormationMD ftSubsea
San Andres5,148-1,780
Clear ForkUPPER CLEARFORK6,640-3,272
Clear ForkLOWER CLEARFORK7,318-3,950

Perforations

Perforated and open-hole intervals.

FromToType
5,1485,164Perforated
6,6407,350Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37531717.5340 S
8.6253,07712.251,965 S
5.58,5077.8751,700 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
00Oct 21, 2013Mar 14, 2013—
00Jun 26, 2013Jul 27, 2012Yes

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) and the University Lands library. then paste it into their search.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
0
bbl, all reported
Oct 2020
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000110934H-1 InjectionCanceled Mar 31, 202325,0002,5505,100–6,000

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 0 · prior 12 0

0120192020

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/16537427, documented in the API reference.