WELL · 42-021-31609 · DISTRICT 1

Orts #1

Plugged

Bastrop County · Giddings (Eagleford) field  · Vertical

Orts #1 (API 42-021-31609) is a plugged well in Bastrop County, plugged September 14, 2012, last operated by Hughes Dan A. Company L.P..

The RRC has issued one drilling permit (amended twice), issued October 22, 2008, permitted to 15,000 ft.

Completion filings report 4 formation tops, including Austin Chalk, Eagle Ford, Sligo, Bossier.

Its 2 leases have reported 112 barrels of oil since April 2009, last reporting in October 2012. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Hughes Dan A. Company L.P.

Based in
Beeville, TX
P-5 status
Active (A)
P-5 last filed
Mar 25, 2026
Permits on file
207
Phone
(361) 358-3752

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHughes Dan A. Company L.P.
Production reportsHughes, Dan A. Company, L.P.through Jul 2012
Latest permitHughes, Dan A. Company, L.P.Jan 28, 2009
15,000
total depth, ft
3
permits on file
Jan 28, 2009
last permit issued
Jul 1, 2011
completed
112
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2009 THROUGH Oct 2012

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 1, 2011
Shut in
—
Plugged
Sep 14, 2012

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
Orts O-3-25863Giddings (Eagleford)Hughes, Dan A. Company, L.P.11120Jul 2011 – Oct 2012
Orts G-1-249715WildcatHughes, Dan A. Company, L.P.100Apr 2009 – Jun 2011

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. 1Hughes, Dan A. Company, L.P.Jul 2011 → Jul 2012

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
673396-97DrillHughes, Dan A. Company, L.P.Aug 19, 2011Jan 28, 2009Nov 4, 200914,090
673396-98DrillHughes, Dan A. Company, L.P.Jan 26, 2009Oct 22, 2008Dec 17, 200815,000
673396-99DrillHughes, Dan A. Company, L.P.Oct 17, 2008Oct 22, 2008Dec 17, 200810,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-1-249715————
—— O-3-25863————

Formation tops

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

FormationMD ftSubsea
Austin Chalk5,840-5,352
Eagle Ford6,530-6,042
Sligo9,195-8,707
Bossier11,945-11,457

Perforations

Perforated and open-hole intervals.

FromToType
6,5406,550Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3751,51217.251,124 S
13.3751,51217.51,124 S
9.6257,23512.251,280 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
00Sep 26, 2012Sep 1, 2011—
00Sep 15, 2009Apr 16, 2009Yes
00Jul 29, 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). 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/02131609, documented in the API reference.