WELL · 42-371-32470 · DISTRICT 8

Boys Ranch State 2-A #2

N

Pecos County · Abell (Clear Fork) field  · Vertical

Boys Ranch State 2-A #2 (API 42-371-32470) is a well in Pecos County operated by Four C Oil & Gas Corp., completed March 23, 1978.

The RRC has issued 2 drilling permits (amended once) between 1978 and 1996, permitted to 4,000 ft.

Its 2 leases have reported 17.9K barrels of oil and 10.3K mcf of gas since January 1993, last reporting in July 2026. The leases carry 3 wells, so these are lease totals, not this well alone.

Operator of record

Four C Oil & Gas Corp.

Dallas, TX · P-5 Y, filed Jan 5, 2024 · 141 permits on file · (214) 534-0306

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleFour C Oil & Gas Corp.
Production reportsN & O Oil Co.through Apr 2026
Latest permitFour C Oil & Gas Corp.Apr 1, 1996

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

4,000
total depth, ft
3
permits on file
Apr 1, 1996
last permit issued
Mar 23, 1978
completed
17.9K
cumulative oil, bbl
10.3K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 23, 1978
Shut in
—
Plugged
—

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 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Boys Ranch State O-10-31786Abell (Permian 2200)N & O Oil Co.217.3K597Jan 1993 – Jul 2026
Boys Ranch State 2-A O-10-26215Abell (Clear Fork)Four C Oil & Gas Corp.16259.7KJan 1993 – Nov 1996

Oil, barrels lease total

Last 12 months 25 · prior 12 30(-17%)

0510202420252026

Chain of custody

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

  1. 1Four C Oil & Gas Corp.Jan 1993 → Jun 2019
  2. 2N & O Oil Co.Jul 2019 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
446421-98RecompletionFour C Oil & Gas Corp.Jun 20, 1996Apr 1, 1996Apr 23, 19962,400
446421-99RecompletionFour C Oil & Gas Corp.Mar 28, 1996Apr 1, 1996—2,400
17494-99DrillB & C Operator'sFeb 2, 1978Feb 2, 1978Feb 10, 19784,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-26215————
—— O-10-31786————

Perforations

Perforated and open-hole intervals.

FromToType
2,3322,348Perforated
3,0433,479Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.375301650 S
13.37530—50 S
8.62556011250 S
8.625560—250 S
2.3752,980——
4.54,0507.875900 S
4.54,050—900 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
00Dec 4, 1996May 13, 1996Yes
00Nov 19, 1996Oct 21, 1980—
00Jan 12, 1984Oct 21, 1980—
00Jan 12, 1984Apr 18, 1978—

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.

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