WELL LOGS · UNITED STATES · ONE ROW PER LOG
Well logs within 2 mi of API 42-417-80146
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.
15 LOG FILES ON 12 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1
| Well | Distancemi | Logas described | Intervalft, as filed | Datereceived |
|---|---|---|---|---|
| Ackers (Morris Sand) Unit #10342-417-38994Shackelford, TX · Grayrock Energy II LLC | 1.18 | RESISTIVITYTIFF | 100 to 3,576 | Jan 29, 2013run Nov 21, 2009 |
| Davis #490842-417-38617Shackelford, TX · Grayrock Energy II LLC | 1.25 | NEUTRON POROSITYTIFF | 1,300 to 3,490 | Jul 26, 2010run Jul 25, 2007 |
| Davis #490842-417-38617Shackelford, TX · Grayrock Energy II LLC | 1.25 | RESISTIVITYTIFF | 0 to 3,511 | Jul 21, 2010run Jul 25, 2007 |
| Ackers (Morris Sand) Unit #10142-417-38991Shackelford, TX · Grayrock Energy II LLC | 1.26 | RESISTIVITYTIFF | 125 to 3,584 | Nov 12, 2012run Nov 7, 2009 |
| Davis #490742-417-38599Shackelford, TX · Grayrock Energy II LLC | 1.33 | RESISTIVITYTIFF | 0 to 4,009 | Jul 2, 2009run Jun 10, 2006 |
| Davis #4917__42-417-38638Shackelford, TX · L.C.S. Production Company | 1.48 | RESISTIVITYTIFF | 0 to 2,334 | May 30, 2018run Dec 8, 2006 |
| Davis #490142-417-38577Shackelford, TX · Grayrock Energy II LLC | 1.49 | RESISTIVITYTIFF | 0 to 3,993 | Apr 23, 2009run Mar 31, 2006 |
| Davis #5006__42-417-38587Shackelford, TX · L.C.S. Production Company | 1.65 | Neutron/Density PorosityTIFFCOMPENSATED NEUTRON/SSD MICROLOG | 1,200 to 4,016 | Jul 21, 2006run May 2, 2006 |
| Davis #5006__42-417-38587Shackelford, TX · L.C.S. Production Company | 1.65 | ResistivityTIFFDUAL INDUCTION | to 4,016 | Jul 21, 2006run May 2, 2006 |
| Davis #470542-417-38581Shackelford, TX · Grayrock Energy II LLC | 1.70 | RESISTIVITYTIFF | 0 to 4,010 | Apr 23, 2009run Apr 22, 2006 |
| Davis #501342-417-38611Shackelford, TX · Grayrock Energy II LLC | 1.70 | RESISTIVITYTIFF | 0 to 4,012 | Dec 10, 2009run Nov 28, 2006 |
| Davis #501042-417-38589Shackelford, TX · Grayrock Energy II LLC | 1.77 | RESISTIVITYTIFF | 0 to 4,002 | Jun 11, 2009run May 12, 2006 |
| Ackers (Morris Sand) Unit #42P42-417-39107Shackelford, TX · Grayrock Energy II LLC | 1.84 | RESISTIVITYTIFF | 120 to 3,653 | Aug 30, 2013run Sep 2, 2010 |
| Davis #502042-417-38698Shackelford, TX · Grayrock Energy II LLC | 1.95 | NEUTRON/DENSITY POROSITYTIFF | 1,500 to 3,536 | May 17, 2011run May 12, 2008 |
| Davis #502042-417-38698Shackelford, TX · Grayrock Energy II LLC | 1.95 | RESISTIVITYTIFF | 132 to 3,556 | May 17, 2011run May 12, 2008 |
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.