WELL · 42-237-33347 · DISTRICT 9

R.F. Martin C #2

Plugged

Jack County · Jack County Regular field  · Vertical

R.F. Martin C #2 (API 42-237-33347) is a plugged well in Jack County, plugged December 18, 2008, last operated by Topco Inc..

The RRC has issued 2 drilling permits (amended once) between 1980 and 1984, permitted to 3,990 ft.

It was permitted by Bandera Petroleum, Inc. and has since transferred to Topco Inc. on the wellbore schedule.

Completion filings report one formation top, including Strawn.

Operator of record

Topco Inc.

Permitted by Bandera Petroleum, Inc.; the EWA schedule now lists a different operator.

Graham, TX · P-5 Y, filed Dec 15, 1989 · 8 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleTopco Inc.
Production reportsBorderline Operating Corp.through Dec 2008
Latest permitTopco, Inc.Oct 3, 1984

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

3,990
total depth, ft
3
permits on file
Oct 3, 1984
last permit issued
—
completed
0
cumulative oil, bbl
45.9K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Dec 2008

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
Dec 18, 2008

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
Martin, R. F. "C" G-13-113046Bartons Chapel, S.(strawn 3100)Borderline Operating Corp.1045.9KJan 1993 – Dec 2008

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. 1Bandera Petroleum, Inc.Jan 1993 → Jan 1998
  2. 2Borderline ProductionFeb 1998 → Feb 2000
  3. 3Borderline Operating Corp.Mar 2000 → Dec 2008

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
253393-98OtherBandera Petroleum, Inc.Aug 31, 1993Oct 3, 1984Sep 4, 19843,750
253393-99RecompletionTopco, Inc.Sep 17, 1984Oct 3, 1984—3,750
91821-99DrillNorris, W. D. I.Sep 8, 1980Sep 8, 1980Sep 2, 19803,990

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-13-113046————

Formation tops

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

FormationMD ftSubsea
StrawnUPPER STRAWN3,438-2,418
StrawnLOWER STRAWN3,763-2,743

Perforations

Perforated and open-hole intervals.

FromToType
3,4393,444Perforated
3,4533,457Perforated
3,7543,762Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62517012.25—
2.3753,734——
4.53,7507.875—
4.5—7.875—

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 6, 1994Aug 31, 1993—
00Oct 26, 1984Oct 5, 1984—
00Oct 25, 1984Sep 11, 1984—
00Jan 12, 1984Apr 7, 1983—

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