TEXAS · WELLS · SHELBY COUNTY · API 42-419-31787 · DISTRICT 06
Congo #2B
Shelby County · Horizontal
- Permitted field
- Carthage (Haynesville Shale)
Congo #2B (API 42-419-31787) is a permitted horizontal well in Shelby County filed by Xto Energy Inc.; no completion report is on file yet.
The RRC has issued 2 drilling permits between 2018 and 2022, permitted to 19,800 ft.
Operator of record
- Based in
- Spring, TX
- P-5 status
- Active – Extension (X)
- P-5 last filed
- Apr 8, 2026
- Permits on file
- 16,156
- Phone
- (346) 502-1572
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | none |
| Latest permit | XTO Energy Inc.Mar 21, 2022 |
- 19,800
- total depth, ft
- 2
- permits on file
- Mar 21, 2022
- last permit issued
- —
- completed
- —
- cumulative oil, bbl
- —
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- —
Surface location
31.816122, -93.903208 NAD27, as filed
31.816293, -93.903397 WGS84
Permit surface location from the RRC GIS record, referenced to NAD27 as the RRC files it; the WGS84 pair is the same point through NOAA's NADCON grid, and the map link uses it, in Shelby County.
Wells nearby
Every well with a location on file around this well, in any state, nearest first.
Texas locations come from drilling permits, so most older Texas wells have none and are not listed.
Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →
Wells named Congo
XTO Energy Inc.'s other wells filed under this lease name in Shelby County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.
Loading the lease's wellsPermits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 878059-99 | Drill | XTO Energy Inc. | Mar 15, 2022 | Mar 21, 2022 | — | 19,800 |
| 835695-99 | Drill | XTO Energy Inc. | Jan 26, 2018 | Feb 1, 2018 | — | 19,800 |
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-419-31787 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-419-31787 → scanned completion filings
Log images filed since 2004 open from the RRC's log search for this well; none are loaded here for it.
Nearby wells and their tops
NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM
Draw a cross-section
This well has no tops filed, so it cannot anchor a section; its neighbors can.
Section of the neighbors →Congo42-419-31784
0.0 KM · XTO Energy Inc. · Section with this well →
| Nacatoch | 1,637 | -1,451 |
| Saratoga | 1,723 | -1,537 |
| Blossom | 2,462 | -2,276 |
| Fredericksburg | 3,189 | -3,003 |
| Paluxy | 3,288 | -3,102 |
| Glen Rose | 3,644 | -3,458 |
| Rodessa | 5,361 | -5,175 |
| James Lime | 5,905 | -5,719 |
11 TOPS · FIRST 8
Crane A-9542-419-30528
5.4 KM · American Operating Company (A) · Section with this well →
| Nacatoch | 1,700 | -1,456 |
| Saratoga | 1,825 | -1,581 |
| Blossom | 2,512 | -2,268 |
| Fredricksberg | 3,254 | -3,010 |
| Paluxy | 3,600 | -3,356 |
| Glen Rose | 3,771 | -3,527 |
| Fredericksburg | 3,872 | -3,628 |
| Glen Rose | — |
13 TOPS · FIRST 8
Shull42-419-31014
6.0 KM · Ellora Energy Inc. · Section with this well →
| Navarro | 1,740 | -1,515 |
| Saratoga | 1,870 | -1,645 |
| Annona | 2,129 | -1,904 |
| Base Annona | 2,393 | -2,168 |
| Base Ammona | 2,393 | -2,168 |
| Ozan | 2,511 | -2,286 |
| Austin Chalk | 2,816 | -2,591 |
Ktulu42-419-31874
6.1 KM · Aethon Energy Operating LLC · Section with this well →
| Nacatoch | 1,753 | -1,527 |
| Saratoga | 1,861 | -1,635 |
| Blossom | 2,505 | -2,279 |
| Fredericksburg | 3,254 | -3,028 |
| Paluxy | 3,472 | -3,246 |
| Glen Rose | 3,766 | -3,540 |
| Rodessa | 5,428 | -5,202 |
| James Lime | 6,038 | -5,812 |
10 TOPS · FIRST 8
Harvester42-419-31876
6.1 KM · Aethon Energy Operating LLC · Section with this well →
| Nacatoch | 1,736 | -1,510 |
| Saratoga | 1,846 | -1,620 |
| Blossom | 2,510 | -2,284 |
| Fredericksburg | 3,250 | -3,024 |
| Paluxy | 3,472 | -3,246 |
| Glen Rose | 3,766 | -3,540 |
| Rodessa | 5,433 | -5,207 |
| James Lime | 6,036 | -5,810 |
10 TOPS · FIRST 8
Harvester42-419-31875
6.1 KM · Aethon Energy Operating LLC · Section with this well →
| Nacatoch | 1,735 | -1,509 |
| Saratoga | 1,844 | -1,618 |
| Blossom | 2,513 | -2,287 |
| Fredericksburg | 3,251 | -3,025 |
| Paluxy | 3,472 | -3,246 |
| Glen Rose | 3,769 | -3,543 |
| Rodessa | 5,433 | -5,207 |
| James Lime | 6,045 | -5,819 |
10 TOPS · FIRST 8
Crane A-9542-419-30322
6.3 KM · American Operating Company (A) · Section with this well →
| Saratoga Chalk | 1,810 | -1,797 |
| Blossom | 2,540 | -2,527 |
| Fredricksberg LS | 3,270 | -3,257 |
| Plug Back TD | 3,590 | -3,577 |
| Paluxy | 3,620 | -3,607 |
Orion Unit42-419-31808
6.4 KM · Aethon Energy Operating LLC · Section with this well →
| Fredericksburg | 3,176 | -2,956 |
| Glen Rose | 3,661 | -3,441 |
| Rodessa | 5,347 | -5,127 |
| James Lime | 5,955 | -5,735 |
| Travis Peak | 6,731 | -6,511 |
| Blossom | — | |
| Saratoga | — | |
| Pettit | — |
10 TOPS · FIRST 8
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/41931787, documented in the API reference.