TEXAS · WELLS · BROOKS COUNTY · API 42-047-01618 · DISTRICT 04

McGill Bros. #378

Plugged

Brooks County · Wildcat field  · Vertical

Mcgill Bros. #378 (API 42-047-01618) is a plugged well in Brooks County, plugged October 24, 1990, last operated by Hilcorp Energy Company.

The RRC has issued one drilling permit, issued November 14, 1980, permitted to 6,700 ft.

It was permitted by Exxon Corp. and has since transferred to Hilcorp Energy Company on the wellbore schedule.

Operator of record

Hilcorp Energy Company

Permitted by Exxon Corp.; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Active – Extension (X)
P-5 last filed
Mar 27, 2026
Permits on file
3,458
Phone
(713) 209-2400

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHilcorp Energy Company
Production reportsnone
Latest permitExxon Corp.Nov 14, 1980

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

6,700
total depth, ft
1
permits on file
Nov 14, 1980
last permit issued
Dec 10, 1980
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH —

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 10, 1980
Shut in
—
Plugged
Oct 24, 1990

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 3 leases this well is completed on; they carry 20 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
— G-4-57666——000—
— O-4-7057——000—
McGill Bros. O-4-9356WildcatOverton Park Oil & Gas LP2000Jan 1993 – —

No volumes reported on these leases in the last three years.

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
99091-99OtherExxon Corp.Nov 14, 1980Nov 14, 1980—6,700

Completions

CompletedLeaseFieldOperatorStatusDepth
Dec 10, 1980McGill Bros. O-4-9356WildcatHilcorp Energy CompanyPlugged—
Oct 21, 1973McGill Bros. G-4-57666Kelsey Deep(zone 21-N N)Exxon Corp.Plugged—
Aug 9, 1967Kelsey Unit O-4-7057Kelsey ( K-2 3 & 4)Exxon Corp.Plugged—
—McGill Bros. O-4-6938Kelsey Deep (Zone 17-B NE)Exxon Corp.Plugged—
—Kelsey Unit O-4-7057Kelsey ( K-2 3 & 4)Exxon Corp.Plugged—

Perforations

Perforated and open-hole intervals.

FromToType
6,4726,481Perforated
—5,465Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37533318.5—
9.6251,53212.25—
2.8756,6798.75—
2.8756,6808.75885 S
2.8756,6908.75—
2.8756,6918.75—

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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Jan 12, 1984Feb 26, 1981—
00Jan 12, 1984Mar 17, 1976—
00Jan 12, 1984Jul 31, 1969—
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 filed since 2004 open from the RRC's log search for this well; none are loaded here for it.

Find logs withinmiles of this well:List →Map →

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