TEXAS · WELLS · ANGELINA COUNTY · RYAN, E. M. UNIT LEASE · API 42-005-30367 · DISTRICT 06
Ryan E. M. Unit #11
Angelina County · Raintree (Travis Peak Cons.) field · Producing · Vertical
Ryan E. M. Unit #11 (API 42-005-30367) is a well in Angelina County operated by Atlas Operating LLC, completed March 31, 2009 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued August 25, 2008, permitted to 11,825 ft.
It was permitted by Encana Oil & Gas(USA) Inc. and has since transferred to Atlas Operating LLC on the wellbore schedule.
Completion filings report 3 formation tops, including James Lime, Pettit, Travis Peak.
Its lease has reported 347 barrels of oil and 1.47M mcf of gas since March 2009, last reporting volume in March 2026.
Operator of record
Permitted by Encana Oil & Gas(usa) Inc.; the EWA schedule now lists a different operator.
- Based in
- Houston, TX
- P-5 status
- Active – Hearing (H)
- P-5 last filed
- Mar 9, 2026
- Permits on file
- 78
- Phone
- (281) 893-9400
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Atlas Operating LLC |
| Production reports | Atlas Operating LLCthrough Mar 2026 |
| Latest permit | Encana Oil & Gas(usa) Inc.Aug 25, 2008 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 11,825
- total depth, ft
- 1
- permits on file
- Aug 25, 2008
- last permit issued
- Mar 31, 2009
- completed
- 347
- cumulative oil, bbl
- 1.47M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Apr 2009 THROUGH Mar 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Mar 31, 2009
- 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 →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Ryan, E. M. Unit G-6-247364 | Raintree (Travis Peak Cons.) | Atlas Operating LLC | 1 | 347 | 1.47M | Mar 2009 – Mar 2026 |
Gas, mcf lease total
Last 12 months 9,531 · prior 12 12,523(-24%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Encana Oil & Gas(usa) Inc.Apr 2009 → Dec 2010
- 2SND Operating, L.L.C.Jan 2011 → Sep 2017
- 3Weatherly Oil & Gas, LLCOct 2017 → Mar 2019
- 4BRG Lone Star Ltd.Apr 2019 → Feb 2026
- 5Atlas Operating LLCMar 2026 → Mar 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 668428-99 | Drill | Encana Oil & Gas(usa) Inc. | Aug 6, 2008 | Aug 25, 2008 | Mar 1, 2009 | 12,300 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Mar 31, 2009 | Ryan E. M. Unit G-6-247364 | Raintree (Travis Peak Cons.) | Atlas Operating LLC | Producing | 11,825 |
Formation tops
As filed on W-2/G-1. Subsea from 310 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| James Lime | 9,556 | -9,246 |
| PettitPETTET | 9,831 | -9,521 |
| Travis Peak | 10,472 | -10,162 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 10,019 | 10,170 | Perforated |
| 10,262 | 10,481 | Perforated |
| 10,688 | 10,998 | Perforated |
| 11,078 | 11,394 | Perforated |
| 11,503 | 11,748 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 3,010 | 11 | 945 S |
| 5.5 | 11,824 | 7.875 | 693 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 →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Jun 18, 2009 | May 16, 2009 | Yes |
| 00 | May 28, 2009 | — | — |
Well logs
1 log loaded from the RRC's log index, the latest received Mar 29, 2012. Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.
Open the RRC's log search for this well ↗| Logas described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| RESISTIVITYSpans James Lime, Pettit, Travis Peak | TIFF | 3,012 to 11,806 | Mar 29, 2012run Mar 21, 2009 | 5.66 |
"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.
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.
- Wellbore filings for 42-005-30367 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-005-30367 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search for it.
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/00530367, documented in the API reference.