OPERATORS · RRC 40171  · P-5 STATUS Y

B & C Texas Oil Properties

B & C Texas Oil Properties has filed no drilling permits in the past 12 months; its most recent permit was issued November 20, 1978.

6 drilling permits have been issued to this operator number since 1977; its P-5 organization report was last filed November 15, 1982.

0
permits, last 12 months
—
vs prior 12 months (0)
0
counties, 12 months
0
producing wells, of 0 of record
0
leases it reports
—
horizontal, 12 months

WINDOWS ON THE RRC ISSUE DATE · COMPUTED OCT 29, 2026

From permit to spud

FROM THE DATES ON ITS W-1 PERMITS · ALL TIME

A permit is a plan, not a well. These figures count only permits old enough to have spudded, six months and more, and read the spud, cancel, and expiry dates the RRC records on each one.

0%
spud rate · 0 of 6 mature permits
—
median days permit to spud
0
spuds, last 180 days
0%
cancelled · 0 permits
6
expired undrilled
3
permits a year over 2 active years

Where

Counties by permits in the last 12 months, with all-time permits and current wells of record there.

County12 moAll timeWellsLast
Comanche county →—60Nov 20, 1978

All 6 permits, searchable → · Leases it reports → · On the map →

Formations in its completed wells

Tops reported on completion filings for wells it operates. RRC wellbore file. About tops →

FormationWellsPermitted last 3 yrs
No completion tops on file.

Production by month

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Barrels on leases where this operator filed the production report. Lease-level by design; the latest months are revised upward as late reports arrive. How production is reported →

0
bbl oil, last 12 reported months
—
vs the 12 months before
0
mcf gas incl. casinghead, last 12
0
bbl oil since reporting began

No lease production reported under this operator number in the last three years.

Beyond the permit record

RRC wellbore file

Wells of record

0
on the schedule
0
producing
0
shut in
0
injection
0
temp. abandoned
0
plugged

How it got them

0
permitted itself
0
acquired from others
6
permitted, now run by others

Acquired means the well's permit names a different operator than the schedule does today. Transfers and operator numbers →

RRC UIC permits · H-10 reported volumes

Disposal and injection

0
active UIC permits of 1
0
permitted bbl/day, active
0
bbl injected, last 12 reported months
Jun 2025
reported through

By county

Comanche0 active0 bbl/d

Permitted volume is a ceiling, not throughput. How to read it →

Permit types

Last 12 months against the prior 12, and all time. A type opens the permit history filtered to it. What the types mean →

Type12 moPrior 12All time
Drill005
Other001

P-5 organization report

As registered with the RRC. About the P-5 →

Registration
Status code Y
Last filed Nov 15, 1982
Address
P.O. Box 1021 % Earl Burns
Abilene, TX 79604
Officers and agents
Scoville, Robert D. · Joint Venturer
Foster, Karen · Joint Venturer
Foster, Lee · Joint Venturer

Latest permits

NEWEST FIRST BY ISSUE DATE · FILED OR ON WELLS IT NOW OPERATES

PermitSeenIssuedOperatorCountyLease / wellDepthAPI
37242Nov 20, 1978Nov 20, 1978B & C Texas Oil PropertiesComancheJackson Estate #130009330202
19912Mar 13, 1978Mar 13, 1978B & C Texas Oil PropertiesComancheHouser, G. & Frost, J. #1-A2,78509330009
1815Jun 27, 1977Jun 27, 1977B & C Texas Oil PropertiesComancheJackson Estate #630009330486
1813Jun 27, 1977Jun 27, 1977B & C Texas Oil PropertiesComancheJackson Estate #930009330485
1710Jun 24, 1977Jun 24, 1977B & C Texas Oil PropertiesComancheJackson Estate #530009330484
1256Jun 21, 1977Jun 21, 1977B & C Texas Oil PropertiesComancheJackson Estate #230009330483

Full permit history →

About this data

Registration from the RRC P-5 organization report, refreshed weekly. Permits from the OGA049M master and daily daf420 files; wells of record from the EWA wellbore schedule; production from PDQ lease reports at the last vintage; disposal from UIC permits and H-10 reports. Summary figures are rebuilt nightly.

Developers: this page as JSON is GET /v1/data/operators/tx/40171, documented in the API reference.