WELL LOGS · UNITED STATES · ONE ROW PER LOG
Well logs within 2 mi of API 42-469-00922
Well logs loaded into Petrora from the regulators' log indexes, newest received first: what each measures, whether it is a digital LAS file or an image, the interval filed for it, and the formations it spans by the well's own tops. Loaded so far for Texas; more states and data sources will follow. Petrora lists these logs; each well's page links to the regulator for the files.
Distances are to the nearest location on file for each well (a horizontal has several along its path), in miles. Locations are surface and path points as mapped, not bottom-hole surveys.
13 LOG FILES ON 13 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1
| Well | Distancemi | Logas described | Intervalft, as filed | Datereceived |
|---|---|---|---|---|
| Pieprzyca #142-469-34016Victoria, TX · Rincon Petroleum Corporation | 1.12 | NEUTRON/DENSITY POROSITYTIFF | 450 to 4,000 | Nov 23, 2009run Oct 31, 2006 |
| Mueller W.A. #142-469-32975Victoria, TX · Bishop J. E. Inc. | 1.27 | Combination: Resistivity/Neutron Density PorosityTIFFDUAL INDUCTION FOCUSED COMPENSATED DENSILOG COMPENSATED NEUTRON GAMMMA RAY | 447 to 4,201 | Aug 16, 2006run Jul 17, 1993 |
| Kalischko #142-469-34007Victoria, TX · Rincon Petroleum Corporation | 1.27 | NEUTRON POROSITYTIFF | 800 to 5,605 | Aug 25, 2009run Sep 1, 2006 |
| House #142-469-34144Victoria, TX · CML Exploration LLC | 1.37 | COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF | 661 to 4,512 | Feb 3, 2014run Dec 31, 2010 |
| Stephen #142-469-33998Victoria, TX · CML Exploration LLC | 1.39 | NEUTRON/DENSITY POROSITYTIFF | 544 to 4,462 | Jul 20, 2009run Jul 18, 2006 |
| Cocke-Goodrich #142-469-34022Victoria, TX · Rincon Petroleum Corporation | 1.52 | COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF | 443 to 3,994 | Dec 7, 2009run Nov 11, 2006 |
| Fishbeck #142-469-33991Victoria, TX · CML Exploration LLC | 1.76 | COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF | 522 to 4,506 | Jun 19, 2009run Jun 23, 2006 |
| C-G Gas Unit #142-469-34027Victoria, TX · Rincon Petroleum Corporation | 1.78 | COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF | 432 to 3,997 | Jan 21, 2010run Dec 31, 2006 |
| Villafranca #1 D42-469-33990Victoria, TX · Ffa Petroleum Services Inc. | 1.79 | COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF | 514 to 4,472 | Jul 20, 2009run Jun 30, 2006 |
| Tali #142-469-34159Victoria, TX · CML Exploration LLC | 1.83 | COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF | 533 to 4,423 | Jun 14, 2012run Apr 30, 2009 |
| Meyer #142-469-34002Victoria, TX · Rincon Petroleum Corporation | 1.86 | COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF | 446 to 3,888 | Aug 28, 2009run Aug 25, 2006 |
| GB #142-469-34176Victoria, TX · CML Exploration LLC | 1.96 | COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF | 513 to 4,416 | Oct 22, 2012run Oct 7, 2009 |
| Lee #142-469-34172Victoria, TX · Amrwr LLC | 2.00 | COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF | 413 to 3,861 | Dec 26, 2012run Nov 5, 2009 |
About this data
Well logs loaded into Petrora from the regulators' log indexes, so far for Texas, with more states and data sources to follow; not necessarily every log that exists. 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. A formation is spanned where the log's filed interval overlaps it in the well's own formation tops; both are measured depths as filed, so a horizontal's lateral is counted in the formation it ends in. Kinds are read from the regulator's description of each log, not from its curves. The date is when the log entered the RRC's imaged log database; a run date is shown where the index gives a different one (mostly logs before 2017: since digital filing began that year, the index gives the filing date for both). Nothing is estimated.
Developers: this page as JSON is GET /v1/data/logs, documented in the API reference.