TEXAS · WELLS · CRANE COUNTY · HARVEY "A" LEASE · API 42-103-35606 · DISTRICT 7B

Harvey A #4303

Plugged

Crane County · Spraberry (Trend Area) field  · Vertical

Harvey A #4303 (API 42-103-35606) is a plugged well in Crane County, plugged January 4, 2016, last operated by Summit Petroleum LLC.

The RRC has issued one drilling permit (amended once), issued October 4, 2008, permitted to 10,900 ft.

Completion filings report 4 formation tops, including Clear Fork, Spraberry, Dean, Wolfcamp.

Its lease has reported 22.7K barrels of oil and 54.9K mcf of gas since June 2008, last reporting in February 2016. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Summit Petroleum LLC

Based in
Midland, TX
P-5 status
Active (A)
P-5 last filed
Feb 17, 2026
Permits on file
1,062
Phone
(432) 682-9800

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSummit Petroleum LLC
Production reportsSummit Petroleum LLCthrough Dec 2015
Latest permitSummit Petroleum LLCOct 4, 2008
10,900
total depth, ft
2
permits on file
Oct 4, 2008
last permit issued
Dec 18, 2008
completed
22.7K
cumulative oil, bbl
54.9K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2008 THROUGH Feb 2016

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 18, 2008
Shut in
—
Plugged
Jan 4, 2016

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; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Harvey "A" O-10-38874Spraberry (Trend Area)Summit Petroleum LLC222.7K54.9KJun 2008 – Feb 2016

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. 1Summit Petroleum LLCJun 2008 → Sep 2015

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
671780-98DrillSummit Petroleum LLCOct 10, 2008Oct 4, 2008Oct 31, 200810,800
671780-99DrillSummit Petroleum LLCSep 24, 2008Oct 4, 2008Oct 30, 200810,900

Completions

CompletedLeaseFieldOperatorStatusDepth
Dec 18, 2008Harvey A O-10-38874Spraberry (Trend Area)Summit Petroleum LLCPlugged—

Formation tops

As filed on W-2/G-1. Subsea from 2,878 ft elevation.Download CSV →

FormationMD ftSubsea
Clear ForkCLEARFORK6,954-4,076
Spraberry7,040-4,162
Dean8,124-5,246
Wolfcamp8,184-5,306

Perforations

Perforated and open-hole intervals.

FromToType
6,9547,156Perforated
6,9548,380Perforated
7,3007,310Perforated
7,4007,599Perforated
8,3608,380Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62539012.25190 S
5.58,5057.875839 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 5, 2009Jul 16, 2009—
00Jun 27, 2009Feb 10, 2009Yes
00Jun 3, 2009——

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