WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-485-02811

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.

Within0.5 mi1 mi2 mi3 mi5 mi10 mi25 miof API 42-485-02811Clear

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.

19 LOG FILES ON 11 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1

Well DistancemiLogas describedIntervalft, as filedDatereceived
Cato N #542-485-45373Wichita, TX · Westneft LLC0.70RESISTIVITYTIFF71 to 1,978Jul 7, 2015run Nov 16, 2012
Moorhouse -B- #642-485-45519Wichita, TX · Sterling Oil and Gas LLC0.87NEUTRON/DENSITY POROSITYTIFF50 to 1,777Dec 30, 2016run Dec 4, 2013
Hearn, S.L. Estate #942-485-38599Wichita, TX0.97RESISTIVITYTIFF20 to 934May 15, 2012run Nov 17, 1982
White a-B #3042-485-45850Wichita, TX · St. Cajetan Oil Company LLC1.07COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF199 to 2,515May 1, 2017run Apr 15, 2015
White a-B #3042-485-45850Wichita, TX · St. Cajetan Oil Company LLC1.07RESISTIVITYTIFF0 to 1,025May 1, 2017run Apr 20, 2015
White a-B #3042-485-45850Wichita, TX · St. Cajetan Oil Company LLC1.07RESISTIVITYTIFF0 to 2,514May 1, 2017run Apr 15, 2015
White a-B #3142-485-45857Wichita, TX · St. Cajetan Oil Company LLC1.12COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF181 to 2,008May 1, 2017run May 1, 2015
White a-B #3142-485-45857Wichita, TX · St. Cajetan Oil Company LLC1.12RESISTIVITYTIFF0 to 1,062May 1, 2017run Jan 12, 2016
White a-B #3142-485-45857Wichita, TX · St. Cajetan Oil Company LLC1.12RESISTIVITYTIFF181 to 2,008May 1, 2017run May 1, 2015
White a-B #3442-485-46310Wichita, TX · St. Cajetan Oil Company LLC1.19Gamma RayLAS + TIFF0 to 2,150Apr 30, 2025
Burnett a #13A42-485-45575Wichita, TX · Hood J. Frank Jr.1.19NEUTRON/DENSITY POROSITYTIFF50 to 2,050Jan 19, 2015run Jun 5, 2014
Burnett a #13A42-485-45575Wichita, TX · Hood J. Frank Jr.1.19RESISTIVITYTIFF50 to 2,050Jan 19, 2015run Jun 5, 2014
Burnett AA #1__42-485-44598Wichita, TX · Hood J. Frank Jr.1.44RESISTIVITYTIFF50 to 1,993Nov 12, 2010run Aug 4, 2010
Texaco-Sun #1142-485-44932Wichita, TX · Hood J. Frank Jr.1.49RESISTIVITYTIFF0 to 833Apr 17, 2012run Jun 3, 2011
Texaco-Sun #1142-485-44932Wichita, TX · Hood J. Frank Jr.1.49RESISTIVITYTIFF50 to 842Apr 17, 2012run May 12, 2011
Texaco-Sun #1342-485-45022Wichita, TX · Hood J. Frank Jr.1.60NEUTRON/DENSITY POROSITYTIFF40 to 1,988Jul 27, 2011run Mar 22, 2011
Texaco-Sun #1342-485-45022Wichita, TX · Hood J. Frank Jr.1.60RESISTIVITYTIFF48 to 1,988Jul 27, 2011run Mar 22, 2011
Burnett a #12A42-485-44951Wichita, TX · LMH Energy1.67RESISTIVITYTIFF50 to 873May 6, 2014run May 18, 2011

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.