WELL · 42-355-30324 · DISTRICT 4

McCann, G.H #33

N

Nueces County  · Vertical

Mccann, G.H #33 (API 42-355-30324) is a permitted well in Nueces County filed by Continental Trend Resources, Inc; no completion report is on file yet.

The RRC has issued 4 drilling permits between 1984 and 2003, permitted to 7,700 ft.

Its 3 leases have reported 1.71K barrels of oil and 786 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

Continental Trend Resources, Inc

Based in
Oklahoma City, OK
P-5 status
Inactive (I)
P-5 last filed
Jan 12, 2022
Permits on file
164
Phone
(405) 234-9000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsContinental Trend Resources, Incthrough Jul 2005
Latest permitContinental Trend Resources, IncFeb 24, 2003
7,700
total depth, ft
4
permits on file
Feb 24, 2003
last permit issued
—
completed
1.71K
cumulative oil, bbl
786
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
McCann, G.H O-4-13178Luby, North (5400)Continental Trend Resources, Inc11.71K786Feb 2003 – Jul 2026
McCann, G.H. O-4-11465Luby (6320)Continental Trend Resources, Inc100Jan 1993 – Dec 2003
McCann, G. H. O-4-13175WildcatContinental Trend Resources, Inc100Oct 2001 – Oct 2003

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. 1Continental Trend Resources, IncFeb 2003 → Jul 2005

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
527769-99RecompletionContinental Trend Resources, IncJan 27, 2003Feb 24, 2003Feb 24, 20035,530
514681-99RecompletionContinental Trend Resources, IncOct 23, 2001Oct 25, 2001Oct 25, 20016,275
333999-99RecompletionKamlok, Inc.Aug 4, 1987Aug 10, 1987—7,700
239738-99RecompletionAmoco Production CompanyMay 17, 1984May 22, 1984—7,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-4-11465————
—— O-4-13175————
—— O-4-13178————

Perforations

Perforated and open-hole intervals.

FromToType
5,4445,450Perforated
6,3196,325Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,26712.25570 S
9.6251,267—570 S
5.57,1558.75720 S
5.57,155—720 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
00Nov 7, 2003Jun 5, 2003Yes
00Oct 31, 2003Oct 2, 2003Yes
00Oct 27, 2003——
00Oct 16, 2003——
00Oct 6, 1988Jun 27, 1988—
00Sep 15, 1988——
00Jan 12, 1984Sep 29, 1972—

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