TEXAS · WELLS · LIPSCOMB COUNTY · PEARL PARKER "710" LEASE · API 42-295-33639 · DISTRICT 08

Pearl Parker 710 #3H

Y

Lipscomb County · Lipscomb (Cleveland) field · Producing  · Horizontal

Pearl Parker 710 #3H (API 42-295-33639) is a horizontal well in Lipscomb County operated by Mewbourne Oil Company, completed March 17, 2011 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued December 30, 2010, permitted to 7,812 ft.

Completion filings report 3 formation tops, including Pennsylvanian, Base Heebner, Cleveland.

Its lease has reported 43.3K barrels of oil and 548K mcf of gas since March 2011, last reporting volume in April 2026.

Operator of record

Mewbourne Oil Company

Based in
Tyler, TX
P-5 status
Active (A)
P-5 last filed
May 21, 2026
Permits on file
2,061
Phone
(903) 561-2900

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMewbourne Oil Company
Production reportsMewbourne Oil Companythrough Apr 2026
Latest permitMewbourne Oil CompanyDec 30, 2010
7,812
total depth, ft
1
permits on file
Dec 30, 2010
last permit issued
Mar 17, 2011
completed
43.3K
cumulative oil, bbl
548K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2011 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Mar 17, 2011
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

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
Pearl Parker "710" G-14-262241Lipscomb (Cleveland)Mewbourne Oil Company143.3K548KMar 2011 – Apr 2026

Gas, mcf lease total

Last 12 months 8,776 · prior 12 9,661(-9%)

05001K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Mewbourne Oil CompanyMar 2011 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
707415-99DrillMewbourne Oil CompanyDec 21, 2010Dec 30, 2010Jan 28, 20118,200

Completions

CompletedLeaseFieldOperatorStatusDepth
Mar 17, 2011Pearl Parker 710 G-14-262241Lipscomb (Cleveland)Mewbourne Oil CompanyProducing7,812

Formation tops

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

FormationMD ftSubsea
PennsylvanianPENN SHALE5,039-2,620
Base Heebner6,143-3,724
Cleveland7,766-5,347

Perforations

Perforated and open-hole intervals.

FromToType
8,15511,540Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,95312.251,200 S
78,1208.7550 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. 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
00Feb 22, 2012Apr 14, 2011Yes

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