WELL · 42-427-33513 · DISTRICT 4

State/LMB Partnership 220 #10

Plugged

Starr County · Rincon (Vicksburg Cons.) field  · Vertical

State/Lmb Partnership 220 #10 (API 42-427-33513) is a plugged well in Starr County, plugged June 11, 2007, last operated by Trap Rock Oil Ltd..

The RRC has issued 2 drilling permits between 2002 and 2004, permitted to 6,900 ft.

It was permitted by Trap Rock Oil Company and has since transferred to Trap Rock Oil Ltd. on the wellbore schedule.

Completion filings report one formation top, including Frio.

Operator of record

Trap Rock Oil Ltd.

Permitted by Trap Rock Oil Company; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Sep 4, 2025 · 41 permits on file · (617) 686-0238

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleTrap Rock Oil Ltd.
Production reportsTrap Rock Oil, Ltd.through Jun 2006
Latest permitTrap Rock Oil CompanyMay 14, 2004

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

6,900
total depth, ft
2
permits on file
May 14, 2004
last permit issued
Oct 1, 2005
completed
0
cumulative oil, bbl
764
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2002 THROUGH Jun 2007

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 1, 2005
Shut in
—
Plugged
Jun 11, 2007

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
State/LMB Partnership 220 G-4-213099Rincon (Vicksburg Cons.)Trap Rock Oil, Ltd.10764Oct 2005 – Jun 2007
State/LMB Partnership 220 G-4-195943WildcatTrap Rock Oil Company100Oct 2002 – Sep 2005

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. 1Trap Rock Oil, Ltd.Nov 2005 → Jun 2006

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
545719-99RecompletionTrap Rock Oil CompanyMay 14, 2004May 14, 2004May 11, 20056,309
521996-99DrillConoco Inc.Jul 19, 2002Jul 19, 2002Aug 19, 20026,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-195943————
—— G-4-213099————

Formation tops

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

FormationMD ftSubsea
Frio3,490-3,110

Perforations

Perforated and open-hole intervals.

FromToType
3,4903,530Perforated
4,1524,163Perforated
4,2804,290Perforated
5,1205,123Perforated
5,1625,165Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
75208.75225 S
4.56,1976.25427 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
00Mar 27, 2006Dec 12, 2005—
00Jan 9, 2006——
00Aug 21, 2003Jul 28, 2003Yes
00Aug 12, 2003——

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