WELL · 42-203-30203 · DISTRICT 6

Davidson #7

Plugged

Harrison County · Trace North (Woodbine) field  · Vertical

Davidson #7 (API 42-203-30203) is a plugged well in Harrison County, plugged July 3, 2024, last operated by Rose City Resources LLC.

The RRC has issued one drilling permit, issued December 15, 1977, permitted to 4,000 ft.

It was permitted by San Juan Exploration Company and has since transferred to Rose City Resources LLC on the wellbore schedule.

Its lease has reported 6.24K barrels of oil and 21 mcf of gas since January 1993, last reporting in September 2024.

Operator of record

Rose City Resources LLC

Permitted by San Juan Exploration Company; the EWA schedule now lists a different operator.

Tyler, TX · P-5 Y, filed May 4, 2026 · 213 permits on file · (903) 245-4495

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleRose City Resources LLC
Production reportsTex-OK Energy, Ltd Partnershipthrough Apr 2014
Latest permitSan Juan Exploration CompanyDec 15, 1977

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
1
permits on file
Dec 15, 1977
last permit issued
Dec 1, 1977
completed
6.24K
cumulative oil, bbl
21
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Sep 2024

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 1, 1977
Shut in
—
Plugged
Jul 3, 2024

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
Davidson O-6-10034Trace,north (Woodbine)Rose City Resources, LLC16.24K21Jan 1993 – Sep 2024

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. 1Tex-OK Energy, Ltd PartnershipJan 1993 → Apr 2014

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
14143-99DrillSan Juan Exploration CompanyDec 15, 1977Dec 15, 1977—4,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-6-10034————

Perforations

Perforated and open-hole intervals.

FromToType
760773Perforated
3,7603,773Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.625175——
4.53,824——

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
00May 16, 1989Mar 9, 1989—
00Jan 12, 1984Dec 9, 1977—

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

2.25K
bbl, last 12 reported months
18.1K
bbl, all reported
Mar 1989
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000006220H-1 InjectionPlugged Jul 24, 2024255003,760–3,773

MONTHLY INJECTED, BBL · H-10 · LAST 6 REPORTED MONTHS

Last 12 months 2,248

05001K1989

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