WELL · 42-295-30880 · DISTRICT 10

Battin a & B #2

Plugged

Lipscomb County · Lipscomb (Cleveland) field  · Vertical

Battin A & B #2 (API 42-295-30880) is a plugged well in Lipscomb County, plugged October 21, 2016, last operated by Jones Energy LLC.

The RRC has issued one drilling permit, issued September 11, 1980, permitted to 8,250 ft.

It was permitted by Jernigan, Steve Inc. and has since transferred to Jones Energy LLC on the wellbore schedule.

Its lease has reported 11.4K barrels of oil and 134K mcf of gas since January 1993, last reporting in June 2020. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Jones Energy LLC

Permitted by Jernigan, Steve Inc.; the EWA schedule now lists a different operator.

Oklahoma City, OK · P-5 Y, filed Oct 2, 2020 · 375 permits on file · (855) 398-4633

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleJones Energy LLC
Production reportsJones Energy, Ltd.through Nov 2012
Latest permitJernigan, Steve Inc.Sep 11, 1980

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

8,250
total depth, ft
1
permits on file
Sep 11, 1980
last permit issued
—
completed
11.4K
cumulative oil, bbl
134K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jun 2020

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
Oct 21, 2016

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; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Battin "a" & "B" O-14-4910Lipscomb (Cleveland)Jones Energy, LLC211.4K134KJan 1993 – Jun 2020

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. 1Bradmar Petroleum CorporationJan 1993 → Jul 1995
  2. 2Petroleum Properties Mgmt. Co.Aug 1995 → Oct 1997
  3. 3Petroleum Properties Mgmt Co LLCNov 1997 → Aug 2005
  4. 4Crusader Energy II, LLCSep 2005 → Aug 2006
  5. 5Crusader Energy Group, LLCSep 2006 → Jul 2008
  6. 6Crusader Energy Group Inc.Aug 2008 → Dec 2009
  7. 7Jones Energy, Ltd.May 2010 → Nov 2012

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
92166-99DrillJernigan, Steve Inc.Sep 11, 1980Sep 11, 1980—8,250

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-14-4910————

Perforations

Perforated and open-hole intervals.

FromToType
8,0748,126Perforated
—8,126Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,58912.25850 S
2.8758,002——
4.58,2137.875200 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
00Jan 12, 1984Jul 10, 1981—
00Jan 12, 1984——

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