TEXAS · WELLS · LIPSCOMB COUNTY · TROSPER, M. LEASE · API 42-295-32109 · DISTRICT 08

Trosper M. #3

Plugged

Lipscomb County · Trosper South (Tonkawa) field  · Vertical

Trosper M. #3 (API 42-295-32109) is a plugged well in Lipscomb County, plugged July 26, 2010, last operated by Strat Land Exploration Company.

The RRC has issued one drilling permit, issued January 28, 1993, permitted to 7,500 ft.

Completion filings report 3 formation tops, including Council Grove, Douglas, Tonkawa.

Its lease has reported 33.7K barrels of oil and 87.1K mcf of gas since August 1993, with no volume in the three years through April 2026.

Operator of record

Strat Land Exploration Company

Based in
Tulsa, OK
P-5 status
Inactive (I)
P-5 last filed
Dec 15, 2021
Permits on file
607
Phone
(918) 584-3844

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleStrat Land Exploration Company
Production reportsStrat Land Exploration Companythrough Dec 2008
Latest permitStrat Land Exploration CompanyJan 28, 1993
7,500
total depth, ft
1
permits on file
Jan 28, 1993
last permit issued
Aug 11, 1993
completed
33.7K
cumulative oil, bbl
87.1K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 1993 THROUGH Dec 2008

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Aug 11, 1993
Shut in
—
Plugged
Jul 26, 2010

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
Trosper, M. O-14-6916Trosper, South (Tonkawa)Strat Land Exploration Company133.7K87.1KAug 1993 – Dec 2008

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. 1Strat Land Exploration CompanyAug 1993 → Dec 2008

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
408524-99DrillStrat Land Exploration CompanyJan 27, 1993Jan 28, 1993Feb 5, 19937,500

Completions

CompletedLeaseFieldOperatorStatusDepth
Aug 11, 1993Trosper M. O-14-6916Trosper South (Tonkawa)Strat Land Exploration CompanyPlugged—

Formation tops

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

FormationMD ftSubsea
Council Grove4,278-1,750
Douglas6,414-3,886
Tonkawa7,034-4,506

Perforations

Perforated and open-hole intervals.

FromToType
7,0427,044Perforated
7,0517,058Perforated
7,0697,080Perforated
7,1047,112Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,50012.25610 S
5.57,2507.87562 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
00Sep 8, 1993Aug 19, 1993Yes
00Aug 26, 1993——

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