WELL · 42-009-39914 · DISTRICT 9

4P Bar Ranch A #2

Y

Archer County · Archer County Regular field · Producing  · Vertical

4p Bar Ranch A #2 (API 42-009-39914) is a well in Archer County operated by TB Petroleum LLC, completed April 15, 1988 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued March 11, 1988, permitted to 4,990 ft.

It was permitted by Hughes & Palmer, Inc. and has since transferred to TB Petroleum LLC on the wellbore schedule.

Completion filings report one formation top, including Strawn.

Its lease has reported 30.8K barrels of oil and 64 mcf of gas since January 1993, last reporting in July 2026.

Operator of record

TB Petroleum LLC

Permitted by Hughes & Palmer, Inc.; the EWA schedule now lists a different operator.

Petrolia, TX · P-5 Y, filed May 4, 2026 · 1 permits on file · (940) 782-3040

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleTB Petroleum LLC
Production reportsTB Petroleum, LLCthrough Apr 2026
Latest permitHughes & Palmer, Inc.Mar 11, 1988

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

4,990
total depth, ft
2
permits on file
Mar 11, 1988
last permit issued
Apr 15, 1988
completed
30.8K
cumulative oil, bbl
64
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 15, 1988
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

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
4P Bar Ranch "A" O-13-27078Archer County RegularTB Petroleum, LLC130.8K64Jan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 1,447 · prior 12 1,619(-11%)

0100200202420252026

Chain of custody

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

  1. 1H&P OperatingJan 1993 → Feb 1993
  2. 2Palmer, John Inc.Mar 1993 → Feb 1994
  3. 3Palmer, John LLCMar 1994 → Jun 2024
  4. 4TB Petroleum, LLCJul 2024 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
343481-98Field transferHughes & Palmer, Inc.Jun 8, 1988Mar 11, 1988—4,990
343481-99DrillHughes & Palmer, Inc.Mar 4, 1988Mar 11, 1988—4,990

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-27078————

Formation tops

As filed on W-2/G-1. Download CSV →

FormationMD ft
Strawn4,250

Perforations

Perforated and open-hole intervals.

FromToType
4,2504,255Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62510512.2585 S
4.54,6207.875150 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
00Jul 25, 1988May 5, 1988Yes
00Jun 30, 1988——

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